[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

** Changed in: udev (Ubuntu Lucid) Status: Won't Fix => Invalid -- [2.6.32-11 regression] 5 second delay on early boot during usb_id https://bugs.launchpad.net/bugs/510937 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

This bug was fixed in the package linux - 2.6.32-14.20 --- linux (2.6.32-14.20) lucid; urgency=low [ Andy Whitcroft ] * rebuild following the GCC update to match compiler for out of tree modules * Revert "[Config] drbd -- enable" * Revert "ubuntu: drbd -- version 8.3.1" * S

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

Ok testing seems to indicate that there is a .3s general benefit for fixing this for the reference platform. There is also a high probabality of a multi second delay for a large userbase so this seems worth fixing. Testing of some RCU patches is in progress. -- [2.6.32-11 regression] 5 second d

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

As discussed on IRC, there are many instances where we *will* block on it - there's still a udevadm settle in the boot, it's just later than usual. This will add 5s to the boot of any non-KMS machine, any machine with encrypted disks, etc. While that's not our "reference image", it's an important

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

> So the key question is, Is the delay on usb_id actually causing an issue here now that we are not blocking on it? The extra I/O wait/process blocking/etc now costs us .3 seconds (averaged over three reboots, between lucid current and lucid current userspace with -10 kernel, and looked at time un

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

Ok I have isolated this to new locking in the sysfs file read code. This seems to be necessary locking as there was a chance that the values being read could be freed underneath us. Contention between usb_id and khubd (presumably) scanning the hub leads to extended waits usb_id trying to aquire th

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

Ok, I have just discovered that this usb-id is much much quicker, of the order of 0.2s if there is an MMC card in the slot on the machine (Dell mini 10v). Remove it and its back to 5s. ** Changed in: linux (Ubuntu Lucid) Assignee: (unassigned) => Andy Whitcroft (apw) -- [2.6.32-11 regressi

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

** Changed in: linux (Ubuntu Lucid) Importance: High => Medium ** Changed in: linux (Ubuntu Lucid) Status: New => Confirmed -- [2.6.32-11 regression] 5 second delay on early boot during usb_id https://bugs.launchpad.net/bugs/510937 You received this bug notification because you are a m

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

Discussed with Scott, and we do support booting with by-id symlinks, thus we need to keep usb_id in the initramfs. ** Changed in: udev (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: udev (Ubuntu) Status: New => Won't Fix -- [2.6.32-11 regression] 5 second delay on early bo

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100201-no- initramfs-usb_id.png is the associated bootchart with dropping usb_id from initramfs. -- [2.6.32-11 regression] 5 second delay on early boot during usb_id https://bugs.launchpad.net/bugs/510937 You received this bug notificat

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

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. W

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- [2.6.32-11 regression] 5 second delay on early boot during usb_id https://bugs.launchpad.net/bugs/510937 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ub

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

Confirmed with 2.6.32-12: http://people.canonical.com/~pitti/bootcharts/daniel- lucid-20100128-1-2.6.32-12.png ** Also affects: linux (Ubuntu Lucid) Importance: High Status: New -- [2.6.32-11 regression] 5 second delay on early boot during usb_id https://bugs.launchpad.net/bugs/510937

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

I had a first quick look at this, and it doesn't reproduce with udevadm trigger in the booted system, and not even with init=/bin/bash and starting udev/udevadm trigger manually. ** Description changed: Since the update to 2.6.32-11 from -10, usb_id hangs for 5 seconds. Compare - http://

[Bug 510937] Re: [2.6.32-11 regression] 5 second delay on early boot during usb_id

** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/38202304/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/38202305/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/38202306/ArecordDevices.t