From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: jkeating@redhat.com, "Joerg Pommnitz" <pommnitz@yahoo.com>,
"Chuck Ebbert" <cebbert@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andi Kleen" <ak@suse.de>
Subject: Re: More E820 brokenness
Date: Thu, 27 Sep 2007 17:15:52 -0600 [thread overview]
Message-ID: <20070927231552.GC4755@cosmic.amd.com> (raw)
In-Reply-To: <46FC32FE.9070302@zytor.com>
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.
next prev parent reply other threads:[~2007-09-27 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 22:17 More E820 brokenness H. Peter Anvin
2007-09-27 22:33 ` Jordan Crouse
2007-09-27 22:47 ` H. Peter Anvin
2007-09-27 23:15 ` Jordan Crouse [this message]
2007-09-27 23:22 ` H. Peter Anvin
2007-09-27 23:27 ` H. Peter Anvin
2007-09-27 23:34 ` Jordan Crouse
2007-09-27 23:36 ` H. Peter Anvin
2007-09-27 23:54 ` Jordan Crouse
2007-09-28 0:12 ` H. Peter Anvin
2007-09-28 13:05 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070927231552.GC4755@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=hpa@zytor.com \
--cc=jkeating@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pommnitz@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox