udev hangs for 30s after upgrade

Hello,

I just did an upgrade (normal upgrade, using pacman -Syu, nothing fancy) and I found it hangs on boot/reboot. dmesg didn't really show anything except that it hang for 30s, which is udev timeout in /etc/rc.conf. I downgraded udev to 175 (and mkinitcpio) and things are back to normal (no hang).

On the bootup screen, it showed some message that looked something like "udevd ... seq 'devices/pci000...' killed " and "worker ... terminated by signal 9" (Sorry for vague error message... i couldn't find these message in any of the log files under /var/log, so I just wrote down by hand what I could write down before it went away).

I was wondering what's up with this? If anyone else has this behaviour? Any known solutions/workarounds? I am using Acer AspireOne 722, if this information helps with anything. I can provide with more information too...

EDIT:This is the dmesg with downgraded udev/mkinitcpio, where things were working fine.

Re: udev hangs for 30s after upgrade

Same problem here. Fortunately, udev is waited now for only half a minute (I remember waiting minutes in the past with older boot scripts). Downgrading udev and mkinitcpio seems to fix the problem too.

Re: udev hangs for 30s after upgrade

I had the same problem with a Realtek wireless module (rtl8192ce). On this forum I got the hint that placing the module in question into the MODULES section of /etc/rc.conf would be a workaround. I have tried it and it works for me - system boots fast again .

Re: udev hangs for 30s after upgrade

swordfish wrote:

I had the same problem with a Realtek wireless module (rtl8192ce). On this forum I got the hint that placing the module in question into the MODULES section of /etc/rc.conf would be a workaround. I have tried it and it works for me - sytem boots fast again .

Re: udev hangs for 30s after upgrade

Yeah I wasn't quite as lucky, I made sure to put in the right name and got the exact same errors, just under "Loading User Specified Modules" instead. Luckily blacklisting it worked fine for me, and the i2400m_usb module is useless to me anyway Even before the update when it was loading correctly it was adding a few seconds to my boot.

As far as I can tell so far, nothing is affected but I'm not sure (please correct me if this is cause for concern). It does increase my boot time however and I find that slightly disappointing/inconvenient. I've been searching the web for answers as to what is happening there but I can't seem to find out. Can anyone link me to an article or point me in the right direction so I can try to find out what's going on?

Re: udev hangs for 30s after upgrade

Re: udev hangs for 30s after upgrade

Moderator: Merged threads

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael FaradayYou assume people are rational and influenced by evidence. You must not work with the public much. -- Trilby----How to Ask Questions the Smart Way

Re: udev hangs for 30s after upgrade

For those who are still having problems: The new udev hang is due to the recent commit to the udev as described here. Reading through it, it seems it mostly affects wireless driver, so if you have no idea what module they need to add/blacklist, it's your wireless. You can search through Arch Wiki to find what wifi card you have.

@willbprog127, modifying rc.conf is nothing really to be scared about. You can also read about it in the wiki if you need to understand better so that you can be more comfortable with what you're editing. I would say it's an essential part of using Arch linux, so get used to it

Re: udev hangs for 30s after upgrade

kcirick wrote:

@willbprog127, modifying rc.conf is nothing really to be scared about. You can also read about it in the wiki if you need to understand better so that you can be more comfortable with what you're editing. I would say it's an essential part of using Arch linux, so get used to it

Ah my friend, I am not scared to edit it...I have made many changes to it through the months I've used Arch. Perhaps I was unclear. I just wish I didn't have to do this to have a smooth boot experience. I will try to find the exact wireless module and add it to MODULES.

Re: udev hangs for 30s after upgrade

kcirick wrote:

For those who are still having problems: The new udev hang is due to the recent commit to the udev as described here. Reading through it, it seems it mostly affects wireless driver, so if you have no idea what module they need to add/blacklist, it's your wireless. You can search through Arch Wiki to find what wifi card you have.

@willbprog127, modifying rc.conf is nothing really to be scared about. You can also read about it in the wiki if you need to understand better so that you can be more comfortable with what you're editing. I would say it's an essential part of using Arch linux, so get used to it

Re: udev hangs for 30s after upgrade

Adding brcmsmac to MODULES in rc.conf fixed the 30 second hang for me, however I still wonder if this is the 'official resolution' to issues like this, or if the developers will fix this problem...surely this kind of workaround is not part of the elegant 'Arch Way', is it?

Re: udev hangs for 30s after upgrade

willbprog127 wrote:

Adding brcmsmac to MODULES in rc.conf fixed the 30 second hang for me, however I still wonder if this is the 'official resolution' to issues like this, or if the developers will fix this problem...surely this kind of workaround is not part of the elegant 'Arch Way', is it?

Its my understanding from the bug report that this is an issue with these effected drivers, and needs to be fixed upstream in the kernel.