Re: udevd: get_netlink_msg: no ACTION in payload found

2005-11-05 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... com

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

2005-10-26 Thread Horms
On Wed, Oct 26, 2005 at 04:03:01AM -0200, Rogério Brito wrote: > 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? I

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Ron Johnson
On Wed, 2005-10-26 at 13:45 +0200, Marco d'Itri wrote: > 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: > > d

Re: 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

Re: 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:

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-26 Thread Marco d'Itri
On Oct 26, Bill Wohler <[EMAIL PROTECTED]> wrote: > Oh yeah, would you say the same about the following warnings? > > Oct 25 15:42:10 olgas udev[9919]: main: action, subsystem or devpath missing Another kernel bug, but this one is known. The sid udev package has a patch to suppress the message

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 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

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 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 s

Re: 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. > > > > > > O

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Henrique de Moraes Holschuh
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 olgas udevd[1109]: get_netlink_msg: no ACTION in payl

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Bill Wohler
Marco d'Itri <[EMAIL PROTECTED]> wrote: > > If this is bug, in which package would you recommend that I report it? > linux-2.6 would be a good start, unless the HAL maintainer has better > ideas about this. Oh yeah, would you say the same about the following warnings? Oct 25 15:42:10 olgas ude

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Bill Wohler
Marco d'Itri <[EMAIL PROTECTED]> wrote: > > If this is bug, in which package would you recommend that I report it? > linux-2.6 would be a good start, unless the HAL maintainer has better > ideas about this. Thanks, will do. -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Bill Wohler
Marco d'Itri <[EMAIL PROTECTED]> 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 olgas udevd[1109]: get_netlink_msg: no ACTION in p

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Marco d'Itri
On Oct 26, Bill Wohler <[EMAIL PROTECTED]> wrote: > If this is bug, in which package would you recommend that I report it? linux-2.6 would be a good start, unless the HAL maintainer has better ideas about this. > Let me know if there is anything more I can do to help with debugging. You should re

udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Bill Wohler
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 olgas udevd[1109]: get_netlink_msg: no ACTION in payload found, skip event 'mount' -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:61

Re: udevd: get_netlink_msg: no ACTION in payload found

2005-10-25 Thread Marco d'Itri
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 olgas udevd[1109]: get_netlink_msg: no ACTION in payload > found, skip event 'mount' Kernel brokeness