During boot, UDev hangs for 15 seconds and eventually kills a worker:
# /var/log/boot Waiting for UDev uevents to be processed [BUSY] ...wait 15 seconds... udevd: worker  timeout, kill it udevd: seq 1459 '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0' killed udevd: worker  terminated by signal 9 (Killed) [DONE]
Others have had this problem, and were able to fix it by finding the culprit module and adding it to rc.conf manually:
$ lspci -vs '0000:00:1a.0' 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 1c77 Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at d3e08000 (32-bit, non-prefetchable) [size=1K] Capabilities:  Power Management version 2 Capabilities:  Debug port: BAR=1 offset=00a0 Capabilities:  PCI Advanced Features Kernel driver in use: ehci_hcd
Here is my addition to rc.conf:
# rc.conf # HARDWARE # -------- MODULES=(ehci_hcd) # added manually USEDMRAID="no" USEBTRFS="no" USELVM="no"
However, boot still hangs and output looks the same. The arch wiki provides solutions(udevd hangs at boot) but these do not work. I'm not too sure what this all means; I can still mount USB sticks and use a USB mouse. It seems to be only affecting my boot time.
Arch is up to date, with kernel 3.2, udev 181-2, and the computer is an ASUS G73jh.
Last edited by sankeytm (2012-03-09 00:28:59)
I had the same problem with my wireless driver. Initially, adding it to MODULES solved it - but the problem recently resurfaced. Another "solution" is available on one of the threads:
1) remove ehci_hcd from MODULES
2) "blacklist ehci_hcd" in /etc/modprobe.d/<anynamehere>.conf
3) add "/sbin/modprobe ehci_hcd" to rc.local
Give that a shot.
Still hangs, but prints out an additional error message:
Mar 4 20:40:25 localhost kernel: [ 8.062959] i2400m_usb 1-1.1:1.0: WiMAX interface wmx0 (64:d4:da:13:90:94) ready Mar 4 20:40:25 localhost kernel: [ 39.235962] i2400m_usb 1-1.1:1.0: boot-mode cmd -1: error waiting for an ack: -4 Mar 4 20:40:25 localhost kernel: [ 39.236137] i2400m_usb 1-1.1:1.0: bootrom init failed: -4 Mar 4 20:40:25 localhost kernel: [ 39.236247] i2400m_usb 1-1.1:1.0: i6050-fw-usb-1.5.sbcf: cannot use: -4, skipping Mar 4 20:40:25 localhost kernel: [ 39.236463] i2400m_usb 1-1.1:1.0: Could not find a usable firmware image Mar 4 20:40:25 localhost kernel: [ 39.236581] i2400m_usb 1-1.1:1.0: cannot bootstrap device: -4 Mar 4 20:40:25 localhost kernel: [ 39.279060] i2400m_usb 1-1.1:1.0: cannot setup device: -4
It seems maybe ehci_hcp was too general, and it was the "usb1/1-1/1-1.1/1-1.1:1.0" that was of importance:
udevd: seq 1459 '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0' killed
Does 1-1.1:1.0 correspond to i2400m_usb ?
Ah, yes, that likely was the wrong module.
There was a point in the other thread to use `lspci -vin <code>' using the trailing portion of what was killled to determine what module it was.
If this is i2400m_usb it you could go back to plan A and put that in MODULES, and keep the above suggestion as plan B.
EDIT: disclaimer, all I really know about this is from my own personal struggle with it, and (more importantly) what I read on this thread, particularly page 4 and on.
Last edited by Trilby (2012-03-05 12:22:23)
edit: plan B actually did not work. It no longer hangs for 15 seconds at the UDev initialization, but instead hangs for 15 seconds at the "network" daemon initialization. Just upgraded to 3.2.9-1-ARCH kernel (udev 181-2) and problem persists.
edit2: just added '@' in front of 'network' in my DAEMONS array. Loads up in parallel and bootup is fast.
Plan B worked:
1) echo "blacklist i2400m_usb" > /etc/modprobe.d/bl_i2400m_usb.conf
2) echo "/sbin/modprobe i2400m_usb" > /etc/rc.local
I actually did this once before, but hadn't added ".conf" to the filename so it didn't work. Otherwise I would not have started a whole new thread; I thought my case was special.
Last edited by sankeytm (2012-03-20 03:53:04)