[gutsy] udevd hogs the processor and spams /var/log/messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: udev
Hello! I've updated from Feisty to Gutsy yesterday, and noticed a weird problem:
Right after boot, a "udevd" process (there are several in the System Monitor) keeps hogging the processor. (This means 100% pretty much all the time. However this is a dual-core machine, it remains responsive.)
I've looked in var/log, and at least "kern.log" and "messages" are spammed by ioctl errors (and I mean tens of megabytes). See below for snippets.
If I do a /etc/init.d/udev restart I get an "Loading additional hardware drivers..." and the scripts remains there (I killed it after a minute or so; the errant process kept hogging). However, "udev stop && udev start" worked, ie. it stopped the processor-hog and restarted udev; I still got an "error receiving uevent message: No buffer space available", but I suppose that's something wrong with a script.
After restarting udev, it doesn't hog the processor anymore nor does it spam the logs; everything seems to work OK until I reboot, when everything happens the same again.
This is an up-to-date Gutsy running on a Latitude D620 laptop (Centrino Duo processor).
$ uname -a
Linux cimer 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
This is what /var/log/kern.log lists (megabytes of it):
Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer kernel: [ 543.860000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
Jun 8 14:19:47 cimer kernel: [ 543.860000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer kernel: [ 543.860000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
Jun 8 14:19:47 cimer kernel: [ 543.860000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer kernel: [ 543.860000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
And this is what /var/log/messages shows:
Jun 8 14:19:47 cimer kernel: [ 543.844000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer kernel: [ 543.848000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer last message repeated 6 times
Jun 8 14:19:47 cimer kernel: [ 543.852000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer last message repeated 7 times
Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table
Jun 8 14:19:47 cimer last message repeated 8 times
Changed in udev: | |
importance: | Undecided → Medium |
status: | Unconfirmed → Confirmed |
I'm having the exact same problem with the identical kernel. Upgraded this morning on my Averatec 3270-EE1 Notebook and it seems to be absolutely mirrored to the above poster.
neo@ubuntu-dev:~$ uname -a
Linux ubuntu-dev 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
Attached are parts from my kern.log and /messages
I haven't tried to boot into another kernel though, though I'll be trying that shortly. Perhaps I might need to simply recompile this existing one as well, but I'll have to test this stuff out later on.
Regards,
Justin