public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc7: udevd compatibility issue?
Date: Fri, 28 Mar 2008 13:22:26 -0700	[thread overview]
Message-ID: <20080328202226.GA16799@suse.de> (raw)
In-Reply-To: <47ED3DDE.3030201@rtr.ca>

On Fri, Mar 28, 2008 at 02:50:06PM -0400, Mark Lord wrote:
> Having coerced 2.6.25-rc7 onto one notebook here,
> we're now working on the other one.
>
> This one is the Dell Lattitude X1 sub-notebook, with Intel everything and 
> 2GB.
>
> On boot, syslog is flooded with "uevent: unsupported action-string;" 
> messages.
> The messages claim "this will be ignored in a future kernel", but this is 
> not a "future kernel".
>
> So, what purpose do they have in 2.6.25-rc7 ?

To tell you nicely that your userspace scripts are doing stupid things
:)

> The system is using udev-079, which came with the distro 2 years ago.

As per the Documentation/CHANGES file, that is not going to work out so
well.

However, this is not udev that is causing the problem, it is your
startup scripts.  Let me guess, ubuntu?

> Mar 28 14:43:29 shrimp syslogd 1.4.1#17ubuntu7.1: restart.

Ah, how did I know.  Yeah, it's their fault, they are writing something
stupid into a sysfs file expecting the kernel just to ignore it.  Try
updating the package and it should go away.  Or you can ignore it for
now, but I'd recommend fixing it.

thanks,

greg k-h

  reply	other threads:[~2008-03-28 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 18:50 2.6.25-rc7: udevd compatibility issue? Mark Lord
2008-03-28 20:22 ` Greg KH [this message]
2008-03-28 22:09   ` Mark Lord
2008-03-28 23:05 ` [PATCH 2.6.25-rc7] fix uevent action-string regression Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080328202226.GA16799@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox