>>> Err, I meant 2.5.64bk4.
>
>> Hmmm ... well I don't see bk4 on ftp.kernel.org,
>
> I meant ftp://ftp.kernel.org/pub/liux/kernel/v2.5/linux-2.5.64.tar.gz
> patched with
> ftp://ftp.kernel.org/pub/liux/kernel/v2.5/snapshots/patch-2.5.64-bk4.gz.
Yeah, I know ... hadn't seemed to have mirrored across when I looked,
but I grabbed it from somewhere else.
> 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.
Right, it *should* work ... Andy wrote the patches to enable that so
that distros could use a common kernel. Maybe it ought to depend on
CONFIG_SMP + HIGHMEM_64GB as well, which would cut out most of the
confusion, but still make it useful for distros.
> Sorry for my misunderstanding of the CONFIG_NUMA configution
> options.
No prob ... should probably be made more obvious. Are you by any chance
doing "yes | make oldconfig"? That's the obvious way to switch it on
by chance ... if so, can I recommend doing "yes '' | make oldconfig"
instead? That'll take the defaults, and work much better in general.
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:22 EST