From: Brian Ristuccia <bristucc@sw.starentnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0 CONFIG_NUMA=y leads to random segfaults
Date: Wed, 21 Jan 2004 17:08:00 -0500 [thread overview]
Message-ID: <20040121220800.GO5555@sw.starentnetworks.com> (raw)
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
next reply other threads:[~2004-01-21 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 22:08 Brian Ristuccia [this message]
2004-01-22 19:33 ` Martin J. Bligh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040121220800.GO5555@sw.starentnetworks.com \
--to=bristucc@sw.starentnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome