From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932113Ab0CaXoK (ORCPT ); Wed, 31 Mar 2010 19:44:10 -0400 Received: from tundra.namei.org ([65.99.196.166]:38739 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753472Ab0CaXoH (ORCPT ); Wed, 31 Mar 2010 19:44:07 -0400 Date: Thu, 1 Apr 2010 10:43:30 +1100 (EST) From: James Morris To: "H. Peter Anvin" cc: Ingo Molnar , Yinghai Lu , linux-kernel@vger.kernel.org, airlied@linux.ie, Thomas Gleixner , Linus Torvalds , Pekka Enberg Subject: Re: Config NO_BOOTMEM breaks my amd64 box In-Reply-To: <4BB3DC4E.7030504@zytor.com> Message-ID: References: <4BB2EB1B.8090303@zytor.com> <20100331185916.GA12306@elte.hu> <4BB3DC4E.7030504@zytor.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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