>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.
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).
>> Sorry for my misunderstanding of the CONFIG_NUMA configution
>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.
I want a kernel that is as broadly hardware compatible as
possible and can take advantage of as much hardware as possible, in
that order. So, I guess I hope to reactivate CONFIG_NUMA once this
problem is solved.
Adam J. Richter __ ______________ 575 Oroville Road
email@example.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."
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/