Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759859AbXI0XQy (ORCPT ); Thu, 27 Sep 2007 19:16:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754342AbXI0XQq (ORCPT ); Thu, 27 Sep 2007 19:16:46 -0400 Received: from outbound-fra.frontbridge.com ([62.209.45.174]:35659 "EHLO outbound4-fra-R.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753364AbXI0XQp (ORCPT ); Thu, 27 Sep 2007 19:16:45 -0400 X-BigFish: VP X-MS-Exchange-Organization-Antispam-Report: OrigIP: 163.181.251.8;Service: EHS X-Server-Uuid: D6C75999-9DAF-4D89-B9AC-C25E3A0BB76A Date: Thu, 27 Sep 2007 17:15:52 -0600 From: "Jordan Crouse" To: "H. Peter Anvin" cc: jkeating@redhat.com, "Joerg Pommnitz" , "Chuck Ebbert" , "Linux Kernel Mailing List" , "Andi Kleen" Subject: Re: More E820 brokenness Message-ID: <20070927231552.GC4755@cosmic.amd.com> References: <46FC2BFD.6070200@zytor.com> <20070927223336.GB4755@cosmic.amd.com> <46FC32FE.9070302@zytor.com> MIME-Version: 1.0 In-Reply-To: <46FC32FE.9070302@zytor.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-OriginalArrivalTime: 27 Sep 2007 23:15:22.0234 (UTC) FILETIME=[4725D5A0:01C8015C] X-WSS-ID: 6AE2E6002ZC502789-01-01 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1163 Lines: 34 On 27/09/07 15:47 -0700, H. Peter Anvin wrote: > Jordan Crouse wrote: > > > > Breaks on the Geode - original behavior. > > > > I think that having boot_prams.e820_entries != 0 makes the kernel > > assume the e820 data is correct. > > > > Okay, now I'm utterly baffled how 2.6.22 ever worked on this Geode, > because this, to the best of my reading, mimics the 2.6.22 behavior > exactly. DID IT REALLY, and/or did you make any kind of configuration > changes? I copied in a 2.6.22 kernel to see that it really did work, and it did. But here's the crazy part - I did a dmesg, and it looks like it *is* using e820 data, and it looks complete (I see the entire map - including the ACPI and reserved blocks way up high). So apparently it was the 2.6.22 code that was buggy, but reading it, I don't immediately see how. Jordan -- Jordan Crouse Systems Software Development Engineer Advanced Micro Devices, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/