Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5994 - udev hangs system

Attached to Project: Arch Linux
Opened by Johannes Jordan (FoPref) - Tuesday, 12 December 2006, 12:38 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Starting up the system, it hangs on "Loading Udev Uevents". This happened several times on two different machines, kernel 2.6.19-beyond.

Workaround: Hard-reset the system and be luckier next time.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 20 January 2007, 17:38 GMT
Reason for closing:  Fixed
Comment by Gregory (gszczesz) - Thursday, 14 December 2006, 02:24 GMT
I just yesterday upgraded my system and changed over to UDev and same thing happens to me.
I used the new rc.conf and tried having UDEv auto load the modules as well as disabled it. Nothing works.

Halts on: Loading UDev uevents

Comment by Gregory (gszczesz) - Thursday, 14 December 2006, 03:35 GMT
I modified the rc.sysinit to allow me to log in and start start_udev manually, and it runs trigger_device_events and then waits for infinity in wait_for_queue....

Greg
Comment by Gregory (gszczesz) - Thursday, 14 December 2006, 03:39 GMT
o.k. so inside there is the loop:
while ! [ "$loop" -gt 0 -a -d /dev/.udev/queue ] ; do
.... etc ....
loop=$(($loop-1))
done

Well, when I echo $loop, I see it going to 0 and then to negative numbers... It does not stop at 0..
Is that's whats wrong?

Greg
Comment by Gregory (gszczesz) - Saturday, 16 December 2006, 13:29 GMT
The loop I posted above is definetally in error, but I think the core problem is that the /dev directory has almost no devices when we reach the loop which really just waits to make sure all the devices are mounted before exiting start_udev (I think anyways). I'm unfortunetally a novice in unix and don't know where to look or what to track to debug this further.
Comment by Tobias Powalowski (tpowa) - Wednesday, 20 December 2006, 22:13 GMT
is this beyond specific or does this happen in stock kernel too?
Comment by Marcel (ferkulat) - Wednesday, 17 January 2007, 22:56 GMT
Yes, it happens on stock kernel26 2.6.19.2-1 (udev-104-1) too.

Loading...