From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Fox Subject: Re: 2.6.18-mm2 boot failure on x86-64 Date: Fri, 06 Oct 2006 13:03:50 -0500 Message-ID: <1160157830.29690.66.camel@flooterbu> References: <20060928014623.ccc9b885.akpm@osdl.org> <200610052105.00359.ak@suse.de> <1160080954.29690.44.camel@flooterbu> <200610052250.55146.ak@suse.de> <1160101394.29690.48.camel@flooterbu> <20061006143312.GB9881@skynet.ie> <20061006153629.GA19756@in.ibm.com> <20061006171105.GC9881@skynet.ie> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Vivek Goyal , Andi Kleen , Badari Pulavarty , Martin Bligh , Andrew Morton , lkml , netdev@vger.kernel.org, kmannth@us.ibm.com, Andy Whitcroft Return-path: Received: from e31.co.us.ibm.com ([32.97.110.149]:29359 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S1422794AbWJFSD6 (ORCPT ); Fri, 6 Oct 2006 14:03:58 -0400 To: Mel Gorman In-Reply-To: <20061006171105.GC9881@skynet.ie> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 2006-10-06 at 18:11 +0100, Mel Gorman wrote: > On (06/10/06 11:36), Vivek Goyal didst pronounce: > > Where is bss placed in physical memory? I guess bss_start and bss_stop > > from System.map will tell us. That will confirm that above memset step is > > stomping over bss. Then we have to just find that somewhere probably > > we allocated wrong physical memory area for bootmem allocator map. > > > > BSS is at 0x643000 -> 0x777BC4 > init_bootmem wipes from 0x777000 -> 0x8F7000 > > So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously > pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible > fix is below. It adds a check in bad_addr() to see if the BSS section is > about to be used for bootmap. It Seems To Work For Me (tm) and illustrates > the source of the problem even if it's not the 100% correct fix. I was able to boot the machine with Mel's patch applied on top of -git22. -- Steve Fox IBM Linux Technology Center