public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.1 on Fedora Core 6 breaks LVM/vgscan
Date: Wed, 30 May 2007 15:22:14 -0400	[thread overview]
Message-ID: <20070530192214.GC2794@redhat.com> (raw)
In-Reply-To: <46585F02.6060806@tmr.com>

On Sat, May 26, 2007 at 12:23:30PM -0400, Bill Davidsen wrote:
 > 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 haven't had any problem booting with any of the kernels, but when I 
 > try to build a kernel with a Fedora config from /boot, it builds fine 
 > but doesn't boot after install. I started by building a very basic 
 > kernel for testing, and then started adding features to get everything I 
 > need. But just using the latest FC6 config file gets me a kernel which 
 > fails in just the way you mention.

9 times out of 10 it's a busted initrd.
Pull it apart and check that the relevant storage modules & their dependancies
are present.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-05-30 19:22 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
2007-05-21 23:12   ` Jonathan Woithe
2007-05-26 16:23 ` Bill Davidsen
2007-05-30 19:22   ` Dave Jones [this message]
  -- 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=20070530192214.GC2794@redhat.com \
    --to=davej@redhat.com \
    --cc=davidsen@tmr.com \
    --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