Re: 2.5.64bk5: X86_PC + HIGHMEM boot failure

[William Lee Irwin III]

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