[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080304104312.457ba3a8.akpm@linux-foundation.org>
Date: Tue, 4 Mar 2008 10:43:12 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Greg KH <gregkh@...e.de>, "Zhang, Rui" <rui.zhang@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
kay.sievers@...y.org, "Rafael J. Wysocki" <rjw@...k.pl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...ru>, dm-devel@...hat.com
Subject: Re: 2.6.25-rc regression: kernel panic on boot
On Tue, 4 Mar 2008 14:54:47 +0100 Ingo Molnar <mingo@...e.hu> wrote:
> * Greg KH <gregkh@...e.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists