inotify_add_watch(6, (null), 10) failed: Bad address

Bug #441367 reported by S1 on 2009-10-03
This bug affects 12 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)

Bug Description

При загрузке появляются сообщения
udevd[828]: inotify_add_watch(6, (null), 10) failed: Bad address
Что это???

S1 (blin) wrote :
ORTEGA (jose-ortega13) on 2009-10-03
affects: ubuntu → udev (Ubuntu)

Needs investigating, sounds like it's getting a NULL pathname for the device node?

Changed in udev (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
S1 (blin) wrote :

Now I do not see these messages. I have last update and аppearance of loading has a little varied.

summary: - udevd[828]: inotify_add_watch(6, (null), 10) failed: Bad address
+ inotify_add_watch(6, (null), 10) failed: Bad address
Changed in udev (Ubuntu):
importance: Medium → High
Chris Medinger (chris-medinger) wrote :

Had the same issue with an upgrade (using kpackagekit) from jaunty to karmic (final). I had had issues with the installer b/c of acpi functions and had to reboot in amidst upgrade. After rebook my / and swap would not mount. Fiddled around, got it them to mount (in an emergency shell). Ran apt-get dist-upgrade, which told me to do dpkg --configure -a, which I did, and then after that at least I could get into kde ( it's a kubuntu system). After some updates, including some udev libraries I was still running into the inotify message. Tried:

   dpkg-reconfigure initramfs-tools

and that did the trick.

hope that helps!

Gloom (tokarevegorka) wrote :

to Chris Medinger:
Unfortunately hasn't helped. This error message had appeared after upgrade from jaunty to karmic (beta).

Niko Ehrenfeuchter (he1ix) wrote :

There has recently been reported a similar bug to this one (although I suppose it is *not* a real duplicate of this one), concerning partitions declared as physical volumes for LVMs: #581566

Rolf Leggewie (r0lf) on 2011-10-19
Changed in udev (Ubuntu Karmic):
status: Triaged → Won't Fix
Simon Rodan (simon-rodan) wrote :

The problem went away for a while but has now returned - I think it came back with 3.2.0-28

I've just updated the kernel to 3.2.0-29-generic and this pic (attached) is with 3.2.0-29

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers