From: William Lee Irwin III <wli@holomorphy.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: mbligh@aracnet.com, gone@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.64bk5: X86_PC + HIGHMEM boot failure
Date: Mon, 10 Mar 2003 00:57:54 -0800 [thread overview]
Message-ID: <20030310085754.GC20188@holomorphy.com> (raw)
In-Reply-To: <200303100846.AAA09348@baldur.yggdrasil.com>
On Sun, 09 Mar 2003, Martin J. Bligh wrote:
>> changes are in my tree ... I've just checked it, and it doesn't
>> do that for me. It should *allow* you to turn on CONFIG_NUMA
>> (and that might be broken for PCs still) but it shouldn't be on
>> by default ... could you check that you can still disable it?
>> Works for me ...
On Mon, Mar 10, 2003 at 12:46:05AM -0800, Adam J. Richter wrote:
> Oops. You're right it is possible to deactivate
> CONFIG_NUMA in this kernel under X86_PC, and that avoids
> the problem. I guess there still is the minor issue that
> either CONFIG_NUMA should work with X86_PC + HIGHMEM (even
> on machines without high memory) or else CONFIG_NUMA
> should not be selectable in this case, but that's obviously
> a bug of much less importance.
> Sorry for my misunderstanding of the CONFIG_NUMA configution
> options.
It might help if we could get bootlogs or backtraces from you.
-- wli
next prev parent reply other threads:[~2003-03-10 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 8:46 2.5.64bk5: X86_PC + HIGHMEM boot failure Adam J. Richter
2003-03-10 8:57 ` William Lee Irwin III [this message]
2003-03-10 15:14 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 19:39 Adam J. Richter
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-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=20030310085754.GC20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=adam@yggdrasil.com \
--cc=gone@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.