public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Guillaume Chazarain <guichaz@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc3 does not like an old udev (071)
Date: Sun, 30 Jul 2006 13:41:01 -0700	[thread overview]
Message-ID: <20060730204101.GA21794@kroah.com> (raw)
In-Reply-To: <44CCEC96.3020607@yahoo.fr>

On Sun, Jul 30, 2006 at 07:29:58PM +0200, Guillaume Chazarain wrote:
> Hi,
> 
> When updating only the kernel to 2.6.18-rc3 on Ubuntu Dapper/x86, 
> /dev/usblp0
> is no more created on boot. If I manually create it, it works fine.
> 
> Vanilla udev from Dapper: version 079 (Documentation/Changes requires
> udev 071 ;-) ).
> 
> git-bisect told me the culprit was
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bd00949647ddcea47ce4ea8bb2cfcfc98ebf9f2a
> 
> Reverting only this commit makes an Oopsing kernel.
> 
> This patch was next to last in its serie:
> http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg44538.html
> 
> Reverting the last patch in the serie (as well as the culprit found by 
> git bisect):
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=43104f1da88f5335e9a45695df92a735ad550dda
> fixes the problem.
> 
> Updating udev to 096, and using a normal 2.6.18-rc3 kernel works too, so 
> maybe
> the correct (albeit unpopular) fix is to update the udev requirement in
> Documentation/Changes?

No, I'm going to revert the above change, as I didn't realize that we
needed a change to udev to support it.  I'll wait until the next major
release for that, and other changes that will require an update to udev
version 081 (released back in January).

But upgrading udev sure doesn't hurt anything :)

thanks,

greg k-h

      parent reply	other threads:[~2006-07-30 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 17:29 2.6.18-rc3 does not like an old udev (071) Guillaume Chazarain
2006-07-30 17:43 ` Jesper Juhl
2006-07-30 18:01   ` Brad Campbell
2006-07-30 20:41   ` Greg KH
2006-07-30 18:58 ` bert hubert
2006-07-30 20:41 ` Greg KH [this message]

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=20060730204101.GA21794@kroah.com \
    --to=greg@kroah.com \
    --cc=guichaz@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    /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