Latest Jaunty udev generates lots of change events

[Peter Klotz]

Binary package hint: udev

Since installing udev 138-1 booting of my Jaunty system (2.6.28-8, amd64) takes very long. udev produces high CPU load and the HDD is continuously accessed.

Starting "udevadm monitor --kernel" shows these messages continuously (sda is the internal HDD):

UEVENT[1235289739.054816] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2 (block)
UEVENT[1235289739.061110] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2 (block)
UEVENT[1235289739.144026] change /devices/virtual/block/dm-2 (block)
UEVENT[1235289739.145231] change /devices/virtual/block/dm-2 (block)
UEVENT[1235289739.148102] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3 (block)
UEVENT[1235289739.148850] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3 (block)
UEVENT[1235289739.156549] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda4 (block)
UEVENT[1235289739.228490] change /devices/virtual/block/dm-0 (block)
UEVENT[1235289739.403233] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda (block)
UEVENT[1235289739.419449] change /devices/virtual/block/dm-0 (block)
UEVENT[1235289739.434304] change /devices/virtual/block/dm-0 (block)
UEVENT[1235289739.440239] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1 (block)
UEVENT[1235289739.442534] change /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1 (block)

I assume this udev changelog entry (http://changelogs.ubuntu.com/changelogs/pool/main/u/udev/udev_138-1/changelog) has something to do with it:

  * New upstream release:
    - Block device nodes watched with inotify for changes and
      /dev/disk/by-{uuid,label} updated automatically.

[Aurius Bendikas Chang (aurius-bendikas)]

Same on my machine. After updates of udev today the system does not boot. It prints to tty1: /sys/devices/pci0000:00/0000:00:0f.0/host0/target0:0:1/0:0:1:0/block/sdb/sdb1 (XXXXX) for about 3 hours. XXXXX - is a number form 0 to somewhere 70000.

After that it hangs with kernel panic: out of memory.

Any ideas how to boot up the system without reinstalling?

[Aurius Bendikas Chang (aurius-bendikas)]

Forgot to mention that I have LVM2 with 3 physical drives in a group. And everything is on LVM. Will provide any other nessesary info. Just ask.