From: Andi Kleen <ak@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: brad@danga.com, jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB
Date: Wed, 13 Oct 2004 23:21:04 +0200 [thread overview]
Message-ID: <20041013232104.7e8dd97e.ak@suse.de> (raw)
In-Reply-To: <416D9139.1060200@osdl.org>
On Wed, 13 Oct 2004 13:34:01 -0700
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> > Who's responsible for the K8_NUMA stuff? I'd love to work with them to
> > narrow this down.
>
> Andi Kleen (SUSE). Copied.
It looks like memory corruption somewhere. I suspect not directly related to NUMA,
but the different memory layout with NUMA may trigger it.
I would enable CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC and see if that
triggers it elsewhere.
First suspection would be the device driver. Perhaps you can test it with
a different block device?
-Andi
next prev parent reply other threads:[~2004-10-13 21:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 19:11 [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB Brad Fitzpatrick
2004-10-13 20:01 ` Jeff Garzik
2004-10-13 20:09 ` Brad Fitzpatrick
2004-10-13 20:12 ` Randy.Dunlap
2004-10-13 20:32 ` Brad Fitzpatrick
2004-10-13 20:34 ` Randy.Dunlap
2004-10-13 21:21 ` Andi Kleen [this message]
2004-10-14 6:07 ` Brad Fitzpatrick
2004-10-14 18:29 ` Brad Fitzpatrick
2004-10-14 18:40 ` Andi Kleen
2004-10-13 20:45 ` Jeff Garzik
2004-10-13 20:49 ` Brad Fitzpatrick
2004-10-13 20:50 ` Jeff Garzik
2004-10-13 20:38 ` Gnome-2.8 stoped working on kernel-2.6.9-rc4-mm1 Stef van der Made
2004-10-13 20:47 ` Radoslaw Szkodzinski
2004-10-13 21:16 ` Stef van der Made
2004-10-13 22:08 ` Buddy Lucas
2004-10-13 23:07 ` Jon Masters
2004-10-13 21:13 ` Jesse Stockall
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=20041013232104.7e8dd97e.ak@suse.de \
--to=ak@suse.de \
--cc=brad@danga.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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