From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>, "Zhang, Rui" <rui.zhang@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kay.sievers@vrfy.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexey Dobriyan <adobriyan@sw.ru>,
dm-devel@redhat.com
Subject: Re: 2.6.25-rc regression: kernel panic on boot
Date: Tue, 4 Mar 2008 10:43:12 -0800 [thread overview]
Message-ID: <20080304104312.457ba3a8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080304135447.GD32383@elte.hu>
On Tue, 4 Mar 2008 14:54:47 +0100 Ingo Molnar <mingo@elte.hu> wrote:
> * Greg KH <gregkh@suse.de> wrote:
>
> > On Mon, Mar 03, 2008 at 07:25:49AM +0800, Zhang, Rui wrote:
> > > Hi, all,
> > >
> > > kernel panic on boot when I try to run 2.6.25-rc1 and later, but 2.6.24-rc8 boots okay.
> > > The result of git-bisect shows that
> > > edfaa7c36574f1bf09c65ad602412db9da5f96bf is first bad commit.
> > >
> > > The git-bisect-result and the dmesg log when the kernel panic are
> > > attached. Any help on this please? :)
> >
> > Are you using LVM? If so, please either upgrade your userspace/initrd
> > stuff, or enable CONFIG_SYSFS_DEPCRECATED
>
> we _really_ must handle this differently and this _is_ a regression that
> multiple people have spent hours on bisecting already ...
>
> So "enable CONFIG_SYSFS_DEPCRECATED" is _NOT_ the right answer, and this
> has been pointed out to you in the past.
Isn't the device-mapper kernel code capable of detecting the older userspace
version and loudly warning about it? That at least would prevent us from
wasting lots of people's time like this.
next prev parent reply other threads:[~2008-03-04 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 23:25 2.6.25-rc regression: kernel panic on boot Zhang, Rui
2008-03-03 22:42 ` Greg KH
2008-03-03 18:33 ` Zhang, Rui
2008-03-04 13:54 ` Ingo Molnar
2008-03-04 18:43 ` Andrew Morton [this message]
2008-03-04 19:33 ` Greg KH
2008-03-04 20:04 ` Linus Torvalds
2008-03-04 20:24 ` Greg KH
2008-03-05 13:25 ` Ingo Molnar
2008-03-05 1:19 ` [dm-devel] " Alasdair G Kergon
2008-03-05 10:16 ` Alexey Dobriyan
2008-03-05 13:29 ` Ingo Molnar
2008-03-05 15:37 ` Greg KH
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=20080304104312.457ba3a8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@sw.ru \
--cc=dm-devel@redhat.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.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