From: Joerg Pommnitz <pommnitz@yahoo.com>
To: Jordan Crouse <jordan.crouse@amd.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: jkeating@redhat.com, Chuck Ebbert <cebbert@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>
Subject: AW: More E820 brokenness
Date: Thu, 27 Sep 2007 23:19:39 -0700 (PDT) [thread overview]
Message-ID: <125549.77407.qm@web51401.mail.re2.yahoo.com> (raw)
Hello all,
I won't be able to test anything before next Tuesday, but I'm with
Jordan on this one. Have a look at the dmsg output I sent you some
time ago (http://article.gmane.org/gmane.linux.kernel/584681).
This was as plain from Linus' tree as you get it (git bisect, make defconfig, make)
and I see:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001e7b0000 (usable)
BIOS-e820: 000000001e7b0000 - 000000001e7bffc0 (ACPI data)
BIOS-e820: 000000001e7bffc0 - 000000001e7c0000 (ACPI NVS)
BIOS-e820: 0000000040400000 - 0000000040440004 (reserved)
BIOS-e820: 00000000f0000000 - 0000000100000000 (reserved) --
Kind regards
Joerg
----- Ursprüngliche Mail ----
Von: Jordan Crouse <jordan.crouse@amd.com>
An: 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>
Gesendet: Freitag, den 28. September 2007, 01:15:52 Uhr
Betreff: Re: More E820 brokenness
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.
__________________________________
Yahoo! Clever: Sie haben Fragen? Yahoo! Nutzer antworten Ihnen. www.yahoo.de/clever
reply other threads:[~2007-09-28 6:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=125549.77407.qm@web51401.mail.re2.yahoo.com \
--to=pommnitz@yahoo.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=hpa@zytor.com \
--cc=jkeating@redhat.com \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®