after upgrade edgy->feisty, high udev CPU usage
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| udev (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: udev
During my upgrade from edgy to feisty (using update-manager), I had a few errors with a few packages, including udev. I simply used apt-get from the command line to complete the installation, which worked fine. (I took notes of which ones had errors, about 10 or so, and apt-get installed them explicitly.)
Anyways, on reboot, the text-mode display was flooded with these messages:
[ 4554.079347] device-mapper: ioctl: error adding target to table
[ 4554.080101] device-mapper: table: 253:1: linear: dm-linear: Device lookup failed
[ 4554.080283] device-mapper: ioctl: error adding target to table
[ 4554.081027] device-mapper: table: 253:1: linear: dm-linear: Device lookup failed
[ 4554.081210] device-mapper: ioctl: error adding target to table
[ 4554.081955] device-mapper: table: 253:1: linear: dm-linear: Device lookup failed
[ 4554.082135] device-mapper: ioctl: error adding target to table
So many that I could barely see what I was typing. When GNOME came up, I saw that my CPU monitor was reported very heavy CPU usage, in an unstable behaviour. (That is, not a straight line, but going up and down quite frequently.)
Using "top", I saw that "udevd" was eating all the CPU.
After "sudo /etc/init.d/udevd stop", the CPU usage returns to normal.
After "sudo /etc/init.d/udevd start", the CPU usage becomes heavy and unstable again.
After stopping udevd, the "dm-linear: Device lookup failed" messages also cease, and start coming again when it is started.
I'm not sure what the fix is, since I don't want to run my system with udevd stopped.
I should note, if it's related, that I'm not using any RAID or LVM partitions.
I have two hard drives, though the system is installed entirely on hdc.
I am running a custom-compiled version of 2.6.19, because I need the BadRAM patch.
Kernel settings are copied from the Ubuntu kernel.
I will reboot to the Ubuntu-provided kernel and report if it makes any difference.
ProblemType: Bug
Date: Sun Mar 4 12:59:37 2007
DistroRelease: Ubuntu 7.04
Uname: Linux hal9000 2.6.19 #1 SMP PREEMPT Tue Feb 27 11:47:09 EST 2007 i686 GNU/Linux
| Stephen Sinclair (radarsat1) wrote | #1 |
| WillDyson (will-dyson) wrote | #2 |
| phaidros (phaidros) wrote | #3 |
| Changed in udev: | |
| status: | Unconfirmed → Fix Released |
| Scudette (scudette) wrote | #4 |
| Sebastian Berthold (sleif) wrote | #5 |
Okay, sorry. Nevermind. I rebooted to the Ubuntu kernel (2.6.20-9-generic) and I did not get the same behaviour. I guess it is related to some upstream kernel bug that has been fixed in later versions. For my part, I removed the dm-mod.ko module, and it "fixed" this problem for me. (Since I am not using LVM I don't need this anyway.)
This bug can be closed.