public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mau <mau@oscar.ping.de>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.1 on Fedora Core 6 breaks LVM/vgscan
Date: Mon, 21 May 2007 20:20:05 +0200	[thread overview]
Message-ID: <20070521182005.GA14390@oscar.prima.de> (raw)
In-Reply-To: <200705210632.l4L6Wkt0004225@turbo.physics.adelaide.edu.au>

On Mon, May 21, 2007 at 04:02:46PM +0930, Jonathan Woithe wrote:
> On 21 May 2007 I wrote:
> 
> > Attempting to compile a 2.6.21.1 kernel for use on a Fedora Core 6 box
> > results in a panic at boot because the root filesystem can't be found.
> 
> I have just compiled 2.6.22-rc2 with the configuration file given in my
> previous post and the resulting kernel successfully boots on the machine
> concerned.  Whatever broke LVM for this machine in between 2.6.18 and
> 2.6.21.1 has now been fixed.

I recall that the device major number was moved to another place (253 ?)
Since this change caused many complaints, it was removed later on ...

> There is still a problem with the CDROM but I will follow up in another
> thread about that.

Did you mention ata_piix ?

With a recent git kernel, which I forgot, I was unable to read or eject
DVD's. (Un-encrypted, BTW).

Current git tree works fine again ...

Patrick


  reply	other threads:[~2007-05-21 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  6:32 2.6.21.1 on Fedora Core 6 breaks LVM/vgscan Jonathan Woithe
2007-05-21 18:20 ` Patrick Mau [this message]
2007-05-21 23:12   ` Jonathan Woithe
2007-05-26 16:23 ` Bill Davidsen
2007-05-30 19:22   ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2007-05-21  5:41 Jonathan Woithe

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=20070521182005.GA14390@oscar.prima.de \
    --to=mau@oscar.ping.de \
    --cc=jwoithe@physics.adelaide.edu.au \
    --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