Bug#671859: udev: Udev hangs on boot for 120 seconds, times out then eats CPU failing to rename files

2012-05-21 Thread eyck
> > /lib/udev/path_id > > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/block/uba > > /lib/udev/udisks-part-id /dev/uba > > Looks like this driver is broken. Kernel bug. Maybe, it might be related to upgrade to 3.3.x, but it doesn't like driver problem, when I re-run the command from

Bug#671859: udev: Udev hangs on boot for 120 seconds, times out then eats CPU failing to rename files

2012-05-21 Thread Marco d'Itri
reassign 671859 linux-2.6 thanks On May 21, eyck wrote: > /lib/udev/path_id > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/block/uba > /lib/udev/udisks-part-id /dev/uba Looks like this driver is broken. Kernel bug. -- ciao, Marco signature.asc Description: Digital signature

Bug#671859: udev: Udev hangs on boot for 120 seconds, times out then eats CPU failing to rename files

2012-05-21 Thread eyck
Package: udev Version: 175-3.1 Followup-For: Bug #671859 Dear Maintainer, On my machines the boot delay is less noticable, but the udev still loops and eats CPU, restart seems to help to a degree, but usually it just keeps on looping and eating up CPU after few minutes. On one machine it seems

Bug#671859: udev: Udev hangs on boot for 120 seconds, times out then eats CPU failing to rename files

2012-05-16 Thread David Headland
Package: udev Version: 175-3.1 Followup-For: Bug #671859 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just as a bit of extra information, I can confirm that within a matter of minutes of re-starting udev, the high CPU usage starts all over again. I'd guess it takes about two minutes, which see

Bug#671859: udev: Udev hangs on boot for 120 seconds, times out then eats CPU failing to rename files

2012-05-07 Thread David Headland
Package: udev Version: 175-3.1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, This bug issue first came to light after upgrading the kernel from 3.0.1 to 3.3.4, both home-build versions from the kernel.org source. Switching back to 3.0.1 stops this behaviour