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#22973 - udev crash during boot

Attached to Project: Arch Linux
Opened by Nicklas W Bjurman (lordmetroid) - Sunday, 20 February 2011, 09:53 GMT
Last edited by Dan McGee (toofishes) - Monday, 07 March 2011, 19:10 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When udev is waiting for messages from processes it crashes with a message, "unable to handle kernel NULL pointer dereference". While I can boot if I press C^c as udev halts the boot, I can not enter X-windows because my file system is not correctly mounted. / becomes ro and my /home is not mounted at all.

I can circumvent this by removing commenting out all manual loading of modules in rc.conf, #MODULES=(lib80211_crypt_tkip wl !b43 !ssb !lib80211 !snd_pcsp !acpi-cpufreq !cpufreq_ondemand)

At first I tried removing alsa and laptop-mode from the loaded daemons, DAEMONS=(syslog-ng !network dbus netfs crond !alsa !@laptop-mode !@openntpd) but that did nothing.

Additional info:
Started as I updated the kernel and got 2.6.37-2 and is still occuring.
I attached my dmeg log

Steps to reproduce:
Probably system specific, right?
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 07 March 2011, 19:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  Opener says latest update fixed issue.
Comment by Nicklas W Bjurman (lordmetroid) - Sunday, 20 February 2011, 09:54 GMT
Forgot to attach the dmesg.log
   dmesg.log (43.3 KiB)
Comment by Nicklas W Bjurman (lordmetroid) - Sunday, 20 February 2011, 10:13 GMT
This is really odd, it seems that at random sometimes I will boot into X and sometimes not, usually the boot seems to stop with the message that the broadcom was loaded.
Comment by Nicklas W Bjurman (lordmetroid) - Sunday, 20 February 2011, 10:31 GMT
As I noticed in my previous comment, it may be broacom that causes all this. I reneabled the alsa daemon even though the log in dmesg says alsa mentions alsa. I did a speaker test without getting sound so maybe both broadcom and alsa is faulty?
   speaker-test.log (1.3 KiB)

Loading...