I took a look at the three udev rules in the initramfs that use usb_id:
* We do not need the hplip permission one from 50-udev-default.rules at all; it will be caught by the udevadm trigger in the real system
* I am pretty sure that we do not need a /dev/disks/by-id/ symlink in the initramfs. We only support UUIDs for file systems, which are generated by blkid, not usb_id.
Thus I jsut removed copying usb_id into the initramfs by commenting out the line in /usr/share/initramfs-tools/hooks/udev. This might be worth doing either way, since it speeds up the time spent in initramfs?
When I do that, I do not get the early 5 s khubd/usb_id blocking any more, and the total boot time again drops from 20 to 15 seconds (just with kernel 2.6.32-10). Instead, I now get a 2.5 s usb_id process hanging off the /etc/init/udevtrigger.conf tree, presumably on the same problematic device. However, it does not slow down the boot any more.
I took a look at the three udev rules in the initramfs that use usb_id:
* We do not need the hplip permission one from 50-udev- default. rules at all; it will be caught by the udevadm trigger in the real system
* I am pretty sure that we do not need a /dev/disks/by-id/ symlink in the initramfs. We only support UUIDs for file systems, which are generated by blkid, not usb_id.
Thus I jsut removed copying usb_id into the initramfs by commenting out the line in /usr/share/ initramfs- tools/hooks/ udev. This might be worth doing either way, since it speeds up the time spent in initramfs?
When I do that, I do not get the early 5 s khubd/usb_id blocking any more, and the total boot time again drops from 20 to 15 seconds (just with kernel 2.6.32-10). Instead, I now get a 2.5 s usb_id process hanging off the /etc/init/ udevtrigger. conf tree, presumably on the same problematic device. However, it does not slow down the boot any more.