[solved] [workaround] udevd-177-3

vwyodajl · 2012-01-21 07:48:00

I am on a fully updated system not running any testing repos and I have multilib enabled. With the new update to udev I am getting a meesage while its starting on boot that I am not sure about, and never saw this until now.

 :: Waiting for UDev uevents to be processed    [BUSY] udevd[277]: worker [283] timeout, kill it
Fri Jan 20 19:55:22 2012: 
Fri Jan 20 19:55:22 2012: udevd[277]: seq 1426 '/devices/pci0000:00/0000:00:1c.4/0000:0a:00.0' killed
Fri Jan 20 19:55:22 2012: 
Fri Jan 20 19:55:22 2012: udevd[277]: worker [283] terminated by signal 9 (Killed)
Fri Jan 20 19:55:22 2012: 
Fri Jan 20 19:55:22 2012:    [DONE]

I also noticed in the new rc.conf there was no longer a UDEV_TIMEOUT option by default so I removed it in mine. On reboot was the first time I saw the message. So thinking that was the cause of the message and needing a timeout I added it back into my rc.conf with =30 and I am still seeing the same thing. I also diff'd all the rest of the rc.conf.pacnew and mine and that was the only real change other than the module and daemons I have in there for my system.

I am not noticing anything not working properly, but just want to figure out what brought this message up.

Thanks for any info and help, google did not help me much on this.

Last edited by vwyodajl (2012-01-21 23:57:57)

CEPfister · 2012-01-21 12:15:48

Same problem here.

juris · 2012-01-21 12:18:15

Yep, same problem.

zacariaz · 2012-01-21 12:23:28

Just did a fresh install 5 minutes ago and have the same problem.

Edit:

Only thing I've done different from last time is appending acpi_osi=Linux as kernel parameter.

Last edited by zacariaz (2012-01-21 12:25:39)

einhard · 2012-01-21 13:06:57

I don't have this issue. Maybe try rebuilding initramfs?

#mkinitcpio -p linux

or other name for your kernel (linux-ck, etc.)

silvik · 2012-01-21 13:40:04

same here. both mainline arch kernel and liquorix.
rebuilding initramfs didn't change a thing.

after waiting some 20-30 seconds for UDev uevents the system boots fine. same error as above "worker xxx terminated by signal 9"

Last edited by silvik (2012-01-21 13:43:44)

archman-cro · 2012-01-21 13:51:11

No issues here with udev 177-3. Boots as normal. No strange messages.

MasterMax · 2012-01-21 14:04:04

same problem, boot fine, after waiting 30 seconds...

falconindy · 2012-01-21 14:54:59

http://www.spinics.net/lists/netdev/msg185742.html

BabyDoc · 2012-01-21 14:56:04

Same message here. Although everything seems to be working fine once booted.

BigMoeW · 2012-01-21 15:46:02

Same problem

CEPfister · 2012-01-21 16:00:57

falconindy wrote:

http://www.spinics.net/lists/netdev/msg185742.html

Indeed, I have a Realtek RTL8188CE 802.11b/g/n WiFi Adapter. (Driver: "rtl8192ce")

Last edited by CEPfister (2012-01-21 16:07:58)

kyoki · 2012-01-21 16:01:41

I get the same message. udev has been quite slow for some time now (still searching around for a solution, maybe it is my graphics card) but the messages are new to me.

[EDIT:] I have brcmsmac in use, so maybe my wifi card makes trouble this time...

regards,
kyoki

Last edited by kyoki (2012-01-21 16:02:57)

tuxfed · 2012-01-21 16:02:58

Same problem. Wifi stopped working. Intel 2915ABG (driver: ipw2200)

Gusar · 2012-01-21 16:04:36

Considering these issues with network cards, was it really a good idea to unleash udev-177 on non-testing users?

tuxfed · 2012-01-21 16:17:10

Got Wifi to work again by downgrading Udev and mkinitcpio (as a dependancy)

miro279 · 2012-01-21 16:43:16

same problem here.. wireless is ipw2100. cannot downgrade as I removed old packages by -Sc already.
can anyone provide old udev package somewhere, or is there any solution in sight?

CEPfister · 2012-01-21 16:43:27

tuxfed wrote:

Got Wifi to work again by downgrading Udev and mkinitcpio (as a dependancy)

How did you do that?

falconindy · 2012-01-21 16:46:25

It would be far wiser to blacklist the module and modprobe it in /etc/rc.local than to downgrade... This is temporary, but the module needs to be fixed in the kernel...

CEPfister · 2012-01-21 17:17:55

falconindy wrote:

It would be far wiser to blacklist the module and modprobe it in /etc/rc.local than to downgrade... This is temporary, but the module needs to be fixed in the kernel...

Just to be sure, you mean : Blacklisting the module in modprobe.conf ("alias mymod off") and adding "MODULES = (mymod)" to rc.conf?

falconindy · 2012-01-21 17:39:48

echo 'blacklist brokenmod' > /etc/modprobe.d/wifi.conf
echo 'modprobe brokenkmod' >> /etc/rc.local

miro279 · 2012-01-21 17:58:30

do we know which module causes the problem? if it is the wireless module(s) thats no solution as we loose wireless support for the time till kernel is fixed. downgrading udev would be a better fix for now! can anyone upload old udev package publicly somewhere? that would be a major help!

CEPfister · 2012-01-21 18:05:31

echo 'blacklist ipw2100' > /etc/modprobe.d/wifi.conf
echo 'modprobe ipw2100' >> /etc/rc.local

This should work just fine for you, because it works great for me. Of course wireless will work after this...

Last edited by CEPfister (2012-01-21 18:07:28)

kcirick · 2012-01-21 18:16:55

Alternate workaround for this is to just put the module name in MODULES=() section in rc.conf. This way you won't need to explicitly blacklist the module in /etc/modprobe.d ... This worked for me

See https://bbs.archlinux.org/viewtopic.php?id=134012

CEPfister · 2012-01-21 20:31:22

kcirick wrote:

Alternate workaround for this is to just put the module name in MODULES=() section in rc.conf. This way you won't need to explicitly blacklist the module in /etc/modprobe.d ... This worked for me
See https://bbs.archlinux.org/viewtopic.php?id=134012

Thanks a lot, it works great !

Arch Linux

#1 2012-01-21 07:48:00

[solved] [workaround] udevd-177-3

#2 2012-01-21 12:15:48

Re: [solved] [workaround] udevd-177-3

#3 2012-01-21 12:18:15

Re: [solved] [workaround] udevd-177-3

#4 2012-01-21 12:23:28

Re: [solved] [workaround] udevd-177-3

#5 2012-01-21 13:06:57

Re: [solved] [workaround] udevd-177-3

#6 2012-01-21 13:40:04

Re: [solved] [workaround] udevd-177-3

#7 2012-01-21 13:51:11

Re: [solved] [workaround] udevd-177-3

#8 2012-01-21 14:04:04

Re: [solved] [workaround] udevd-177-3

#9 2012-01-21 14:54:59

Re: [solved] [workaround] udevd-177-3

#10 2012-01-21 14:56:04

Re: [solved] [workaround] udevd-177-3

#11 2012-01-21 15:46:02

Re: [solved] [workaround] udevd-177-3

#12 2012-01-21 16:00:57

Re: [solved] [workaround] udevd-177-3

#13 2012-01-21 16:01:41

Re: [solved] [workaround] udevd-177-3

#14 2012-01-21 16:02:58

Re: [solved] [workaround] udevd-177-3

#15 2012-01-21 16:04:36

Re: [solved] [workaround] udevd-177-3

#16 2012-01-21 16:17:10

Re: [solved] [workaround] udevd-177-3

#17 2012-01-21 16:43:16

Re: [solved] [workaround] udevd-177-3

#18 2012-01-21 16:43:27

Re: [solved] [workaround] udevd-177-3

#19 2012-01-21 16:46:25

Re: [solved] [workaround] udevd-177-3

#20 2012-01-21 17:17:55

Re: [solved] [workaround] udevd-177-3

#21 2012-01-21 17:39:48

Re: [solved] [workaround] udevd-177-3

#22 2012-01-21 17:58:30

Re: [solved] [workaround] udevd-177-3

#23 2012-01-21 18:05:31

Re: [solved] [workaround] udevd-177-3

#24 2012-01-21 18:16:55

Re: [solved] [workaround] udevd-177-3

#25 2012-01-21 20:31:22

Re: [solved] [workaround] udevd-177-3

Board footer