From: "Adam J. Richter" <adam@yggdrasil.com>
To: mbligh@aracnet.com
Cc: apw@shadowen.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.64bk5: X86_PC + HIGHMEM boot failure
Date: Mon, 10 Mar 2003 11:39:11 -0800 [thread overview]
Message-ID: <200303101939.LAA05514@adam.yggdrasil.com> (raw)
On Mon, 10 Mar 2003, Martin J. Bligh wrote:
>> I just verified that the problem also occurs with NUMA +
>> HIGHMEM_64GB (i.e., it is not limited to HIGHMEM_4GB).
>>
>> By the way, HIGHMEM_64GB without NUMA gets a lot father, but
>> still experiences memory corruption, probably same bug that caused me
>> to downgrade to HIGHMEM_4G months ago (i.e., probably not related to
>> this NUMA problem).
>Yeah, we really ought to fix that. This one?
> http://bugme.osdl.org/show_bug.cgi?id=5
Yes. Thank you for doing such meticulous job of entering it
into bugmse.osdl.org.
[About the original problem of CONFIG_NUMA bombing out on my
384MB machine with a HIGHMEM4G kernel:]
>Right ... I think I have some more patches from Andy somewhere, though
>he may not have tested with 64Gb on his PC ... I'll go look, and send
>them to you if I have.
Great, although it will probably be several hours before I can
test any patches that you send me.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-03-10 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 19:39 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 19:22 Adam J. Richter
2003-03-10 19:18 ` Martin J. Bligh
2003-03-10 17:08 Adam J. Richter
2003-03-10 8:46 Adam J. Richter
2003-03-10 8:57 ` William Lee Irwin III
2003-03-10 15:14 ` Martin J. Bligh
2003-03-09 23:08 Adam J. Richter
2003-03-09 23:05 Adam J. Richter
2003-03-10 6:27 ` Martin J. Bligh
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=200303101939.LAA05514@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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
all inboxes | Powered by JetHome®