Messages in this thread | | | Date | Wed, 21 Jan 2004 17:08:00 -0500 | From | Brian Ristuccia <> | Subject | 2.6.0 CONFIG_NUMA=y leads to random segfaults |
| |
While building a kernel for a Dual Athlon MP 2800 system, I accidentally enabled CONFIG_NUMA, "Numa Memory Allocation Support". This option should have been a no-op on the system I was using it on, since on this motherboard all system memory is equally close to each of the two CPU's. Instead, it caused userspace processes to randomly segfault.
Booting a 2.6.0 rebuilt without CONFIG_NUMA made the problem go away.
-- Brian Ristuccia bristucc@sw.starentnetworks.com - 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/
| |