Bug 533814 - Slow boot, hangup at "Starting udev"
Summary: Slow boot, hangup at "Starting udev"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: udev
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 540650 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-09 12:05 UTC by Ignat Semenov
Modified: 2009-12-07 13:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-09 17:54:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
bootchart (151.52 KB, image/png)
2009-11-09 12:05 UTC, Ignat Semenov
no flags Details

Description Ignat Semenov 2009-11-09 12:05:48 UTC
Created attachment 368190 [details]
bootchart

Description of problem:
Fedora boots very slowly. Hangs when "Starting udev" for approximately 30 seconds. No RPMs had been installed before booting, and this was not the first boot. I've never experienced similar problems with any previous Fedora release.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Harald Hoyer 2009-11-09 12:36:20 UTC
can you attach /var/log/messages and /var/log/dmesg from the last boot only?

Comment 2 Harald Hoyer 2009-11-09 12:39:05 UTC
Do you have the floppy enabled in your BIOS and no real floppy installed?

Comment 3 Ignat Semenov 2009-11-09 17:43:13 UTC
Yes, the floppy was the reason. Disabling it gave me a boot time of 24 seconds (according to bootchart). So this one can be closed.
P.S How did you guess without dmesg output?)

Comment 4 Harald Hoyer 2009-11-09 17:54:01 UTC
similar bug reports and the hanging blkid process, (which seems to try to access the floppy through BIOS routines :)

Comment 5 Michal Schmidt 2009-12-07 13:44:36 UTC
*** Bug 540650 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.