Am 30.04.2015 um 07:55 schrieb Matthias Bodenbinder: > Apr 30 07:28:31 xxx systemd-udevd[175]: worker [196] > /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0 timeout; kill it > Apr 30 07:28:31 xxx systemd-udevd[175]: seq 1229 > '/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0' killed > 55: USB 00.0: 0401 Multimedia audio controller > [Created at usb.122] > Unique ID: IO+7.DGe+0l9GPv1 > Parent ID: Uc5H.TI3vE1oZtwF > SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0 > #### > > udev seems to pause for a long time with very few messages until it > kicks in again at about 07:28:50. One of first message before it kicks > in again is: > > Apr 30 07:28:50 xxx kernel: usbcore: registered new interface driver > snd-usb-audio > Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1603 queued, 'add' 'sound' > Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1604 queued, 'add' 'sound' > > I am wondering if this can have something to do with my usb keyboard > which happens to have a sound module with audio in and out for headset > and mic. And it is also a USB hub where the mouse is connected: As you can see above, systemd-udevd timeouts processing the events from that device and is eventually killed. The internal timeout for udev is 90s. If you add the the remaining time to boot the system, that would explain the 2min boot times. This looks like either buggy hardware or a bug in the kernel. Can you try with a different keyboard and mouse directly attached to your computer, not via a hub? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature