Re: 2.5.64bk5: X86_PC + HIGHMEM boot failure

[Martin J. Bligh]

> 	Under linux-2.5.64bk5, CONFIG_X86_PC sets CONFIG_NUMA,
> which sets CONFIG_DISCONTIGMEM.  This causes the version of
> set_max_mapnr_init in arch/i386/mm/discontig.c to be compiled
> in (instead of the one from arch/i386/mm/init.c):
>
> Err, I meant 2.5.64bk4. 

Hmmm ... well I don't see bk4 on ftp.kernel.org, but the same
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 ...

M.

config NUMA
        bool "Numa Memory Allocation Support"
        depends on (HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT && ACPI && !ACPI_HT_
ONLY))) || X86_PC