I'm also having the hangup on udev processing, but also there's a kernel panic because of a memory leak when loading snd modules. The process is taking all memory available and then I get a kernel panic because of modprobe has eaten all of the available memory. I need to manually kill the processes to go on to desktop. This happened after upgrading kernel to 3.2.1, udev-178-1 and replaced module-init-tools by kmod. Also, I have no sound because my soundcard modules are not loaded (I manually killed the process which loads them)

Re: udev hangs for 30s after upgrade

@blitux

I have similar issue after kmod,udev update. While booting gets stuck with a kernel panic. sometimes I am able to boot successfully and then login. But my soundcard will not be detected. I had to downgrade kmod,udev and mkinitcpio to get everything back in order. Please let me know if you are able to solve your problem.

Re: udev hangs for 30s after upgrade

I have more info. Modprobe hangs up when I try to load snd-hda-intel manually with # modprobe snd-hda-intel. I get "FATAL: Module snd-ioctl32 not found". My soundcard is 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01), HP 530 laptop.

I've checked /etc/modprobe.d/50-sound.conf and see that snd-ioctl32 is being blacklisted when loading snd modules (snd-ioctl32 does not exists at least on 3.2.1-2 kernel). Maybe it's an issue of kmod, because it was working with module-init-tools before the upgrade.

Re: udev hangs for 30s after upgrade

I had exactly the same problem. When I tried to load snd-hda-intel. I got snd-ioctl32 not found error. Everything is fine after the downgrade of udev & kmod.. Dont know where exactly to go from this point.

Re: udev hangs for 30s after upgrade

Well I have fought with this on my system all day. I am running a lenovo w520 using the dedicated graphics.I would not get any errors on boot it would just sit at starting udev, i left it run for 12 hours with no luck.I was able to get into the system with the apci=off noapci kernel options.

After trying a lot of different stuff including adding my wireless driver to rc.conf and rebuilding the initrd image I finally have it fixed.

It turns out it is the kernel that is causing my problem, I downgraded all of my packages (init-modules kernel udev kmod) then started re-upgrading them.

The working config I have now is all of the new packagesudev-179-1kmod-4-1 (replaced init-modules) kernel-3.1.6-1

Everything works great and I have nothing in my modules line in rc.conf.

If I upgrade the kernel to 3.2.1-2 the problem comes back and the system becomes unbootable without the acpi options.

This is a 64bit system 8Gb ram nvidia quadro 1000iwlwifi driver

So far everything is working as I would expect it to, just like before the update.

Hopefully this helps someone, I know I was beating my head against the wall.

Re: udev hangs for 30s after upgrade

Ok, found out how to solve this.The thing is not everyone has problems with the same module. You need to find out which module makes the loading process hang.If you read what the system tells you, you'll see something like this:

Re: udev hangs for 30s after upgrade

bogdan2011 wrote:

Ok, found out how to solve this.The thing is not everyone has problems with the same module. You need to find out which module makes the loading process hang.If you read what the system tells you, you'll see something like this:

Thats very helpful info. What about the few of us who never even get in, I let udev sit for over 12 hours and nothing. Maybe my problem was/is different, I don't seem to have an issue with udev-179-1 or kmod, my problem seems to lay with the 3.2 kernel.

Not trying to hijack this at all, This is just one of the top threads for udev hangs on boot, so I want to make sure all the solutions get seen.

Re: udev hangs for 30s after upgrade

bogdan2011 wrote:

Ok, found out how to solve this.The thing is not everyone has problems with the same module. You need to find out which module makes the loading process hang.If you read what the system tells you, you'll see something like this: