[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1004011042460.32618@tundra.namei.org>
Date: Thu, 1 Apr 2010 10:43:30 +1100 (EST)
From: James Morris <jmorris@...ei.org>
To: "H. Peter Anvin" <hpa@...or.com>
cc: Ingo Molnar <mingo@...e.hu>, Yinghai Lu <yinghai@...nel.org>,
linux-kernel@...r.kernel.org, airlied@...ux.ie,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: Config NO_BOOTMEM breaks my amd64 box
On Wed, 31 Mar 2010, H. Peter Anvin wrote:
> On 03/31/2010 03:58 PM, James Morris wrote:
> > On Wed, 31 Mar 2010, Ingo Molnar wrote:
> >
> >>>
> >>> Yes, it was happening with -rc3.
> >>
> >> Could you please send the bootlog that Yinghai asked for, plus also one that
> >> you get with NO_BOOTMEM turned off (for comparison)?
> >
> > I don't have the old boot logs, and have since upgraded the system
> > further.
> >
>
> Upgraded how? The problem no longer happens?
Upgraded to the latest rawhide userland -- I have not since tested with
bootmem off. I'll try and do so again when I get a chance.
>
> > IIRC, the boot was failing after not being able to find the root fs
> > (ext3/lvm/raid0). I thought it was a dracut issue, but it seemed to be
> > fixed by enabling bootmem.
>
> This would rather match the problem that was addressed by the patch in
> -rc3. Any help in reproducing it would be great.
>
> -hpa
>
--
James Morris
<jmorris@...ei.org>
--
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