From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758421Ab0CaW6z (ORCPT ); Wed, 31 Mar 2010 18:58:55 -0400 Received: from tundra.namei.org ([65.99.196.166]:36609 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758387Ab0CaW6y (ORCPT ); Wed, 31 Mar 2010 18:58:54 -0400 Date: Thu, 1 Apr 2010 09:58:03 +1100 (EST) From: James Morris To: Ingo Molnar cc: "H. Peter Anvin" , 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: <20100331185916.GA12306@elte.hu> Message-ID: References: <4BB2EB1B.8090303@zytor.com> <20100331185916.GA12306@elte.hu> 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, 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. 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. > Also, when did you first hit this bug? This code has been upstream for almost > a month, and it was in linux-next before that - so you should have hit this > much sooner. A rough timeframe would suffice. I suppose you were booting > upstream kernels during the merge window as well? In this case, in the last few days (also when I first saw or noticed the bootmem option). I was booting relatively recent linus kernels during the merge window, although my main work was being done on an older upstream kernel. -- James Morris