linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, Andrey Slepuhin <pooh@t-platforms.ru>,
	Ray Bryant <raybry@mpdtxmail.amd.com>,
	linux-mm@kvack.org, akpm@osdl.org
Subject: Re: [discuss] Memory performance problems on Tyan VX50
Date: Wed, 1 Feb 2006 09:03:15 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0602010900200.16613@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200602011539.40368.ak@suse.de>

On Wed, 1 Feb 2006, Andi Kleen wrote:

> Looks like a bug. There were changes both in the page allocator and in
> mempolicy in 2.6.16rc, so it might be related to that.
> What does this wheremem program do exactly?
> And what does numastat --hardware say on the machine?
> 
> Either it's generally broken in page alloc or mempolicy somehow managed to pass in
> a NULL zonelist. 

The failure is in __rmqueue. AFAIK There is no influence of mempolicy on 
that one. Could we get an accurate pointer to the statement that is 
causing the NULL deref?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-02-01 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43DF7654.6060807@t-platforms.ru>
     [not found] ` <200601311223.11492.raybry@mpdtxmail.amd.com>
     [not found]   ` <43E0B8FE.8040803@t-platforms.ru>
2006-02-01 14:39     ` Andi Kleen
2006-02-01 17:03       ` Christoph Lameter [this message]
2006-02-01 17:16         ` Andi Kleen
2006-02-01 20:26           ` Andrey Slepuhin
2006-02-01 23:59             ` Christoph Lameter
2006-02-02 22:07       ` Ray Bryant

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=Pine.LNX.4.62.0602010900200.16613@schroedinger.engr.sgi.com \
    --to=clameter@engr.sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-mm@kvack.org \
    --cc=pooh@t-platforms.ru \
    --cc=raybry@mpdtxmail.amd.com \
    /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