Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Rogério Brito
On Oct 26 2005, Marco d'Itri wrote: On Oct 26, Bill Wohler [EMAIL PROTECTED] wrote: Oct 25 16:34:21 olgas udevd[1109]: get_netlink_msg: no ACTION in payload found, skip event 'mount' Kernel brokeness? Is some other user space application sending bogus events to the netlink socket (is

Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Henrique de Moraes Holschuh
On Wed, 26 Oct 2005, Rogério Brito wrote: On Oct 26 2005, Henrique de Moraes Holschuh wrote: I see it on mounts caused by automount. I don't see it on mounts caused by mount. So, we have one possible culprit. I see it with manual mounting of removable media (e.g., CDs). Hmm... come to

Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Rogério Brito
On Oct 26 2005, Henrique de Moraes Holschuh wrote: I see it on mounts caused by automount. I don't see it on mounts caused by mount. So, we have one possible culprit. I see it with manual mounting of removable media (e.g., CDs). No automount or autofs here. Hope this helps as a data point,

Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Marco d'Itri
On Oct 26, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: Hmm... come to think of it, that's what I use automout for. It could be removable media, then. Anyway, I can't reproduce it anymore, since 8 days ago: daemon.log.0:Oct 18 00:47:44 khazad-dum udevd[14729]: get_netlink_msg: no

Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Marco d'Itri
On Oct 26, md wrote: Anyway, I can't reproduce it anymore, since 8 days ago: daemon.log.0:Oct 18 00:47:44 khazad-dum udevd[14729]: get_netlink_msg: no ACTION in payload found, skip event 'umount' I have since learnt that these events are generated by the kernel. Why they are broken should

Bug#335814: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Bill Wohler
Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: On Wed, 26 Oct 2005, Marco d'Itri wrote: On Oct 26, Bill Wohler [EMAIL PROTECTED] wrote: Anyone know what this message is all about? This began to appear after a recent upgrade whenever I mount a USB drive. Oct 25 16:34:21