From: Christoph Lameter <clameter@sgi.com>
To: Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!
Date: Mon, 16 Oct 2006 16:37:33 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610161630430.8341@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1161031821.31903.28.camel@farscape>
On Mon, 16 Oct 2006, Will Schmidt wrote:
> This is output from 2.6.18-rc2. MemFree, MemTotal, MemUsed still
> wrong. Node0 slab is still zero. I've also attached the numa=debug
> boot log from this boot, in case it has any clues that were missing from
> the other boot log.
It looks as if node 0 is allready full on bootup. The new code in 2.6.19
controls locality in a more strict form in the slab. 2.6.18 and earlier
were able to tolerate if a request for a page from the slab allocator for
node 0 returns memory on node1 even if node 1 has not been bootstrapped
yet. But this resulted in a problem in the slab because the node lists
dedicated for node 0 now had memory from node 1 in it (which led to
latency problems since slab code subsequently assumes that node local
memory is very fast, which with corrupted per node lists is no longer
true.).
You must bootstrap on a node that has memory available. If you would
bootstrap the slab on node 1 that would work.
> Node 0 MemTotal: 229376 kB
> Node 0 MemUsed: 229376 kB
^^^^^ This node should not be full!!!
Increase memory on node 0 so that the slab can bootstrap.
next prev parent reply other threads:[~2006-10-16 23:37 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 18:41 Will Schmidt
2006-10-13 19:05 ` Christoph Lameter
2006-10-13 19:53 ` Will Schmidt
2006-10-13 20:57 ` Will Schmidt
2006-10-13 21:22 ` Nathan Lynch
2006-10-13 21:34 ` Anton Blanchard
2006-10-13 22:01 ` Mike Kravetz
2006-10-13 22:22 ` Christoph Lameter
2006-10-16 16:00 ` Will Schmidt
2006-10-16 19:20 ` Will Schmidt
2006-10-16 19:25 ` Christoph Lameter
2006-10-16 20:50 ` Will Schmidt
2006-10-16 23:37 ` Christoph Lameter [this message]
2006-10-18 6:11 ` Paul Mackerras
2006-10-18 15:12 ` Christoph Lameter
2006-10-18 21:19 ` Paul Mackerras
2006-10-18 21:26 ` Christoph Lameter
2006-10-18 21:49 ` Christoph Lameter
2006-10-19 5:03 ` Paul Mackerras
2006-10-19 16:16 ` Christoph Lameter
2006-10-19 16:30 ` Anton Blanchard
2006-10-19 16:49 ` Christoph Lameter
2006-10-19 22:23 ` Paul Mackerras
2006-10-19 22:31 ` Christoph Lameter
2006-10-20 7:18 ` Paul Mackerras
2006-10-20 14:18 ` Andy Whitcroft
2006-10-20 14:31 ` [PATCH] Reintroduce NODES_SPAN_OTHER_NODES for powerpc Andy Whitcroft
2006-10-20 16:30 ` Mel Gorman
2006-10-20 14:59 ` kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177! Mike Kravetz
2006-10-20 15:19 ` Will Schmidt
2006-10-20 16:00 ` Andy Whitcroft
2006-10-20 17:09 ` Andrew Morton
2006-10-20 17:46 ` Christoph Lameter
2006-10-20 18:07 ` Andy Whitcroft
2006-10-20 17:13 ` Will Schmidt
2006-10-20 17:34 ` Christoph Lameter
2006-10-20 22:54 ` Paul Mackerras
2006-10-19 17:03 ` Christoph Lameter
2006-10-19 18:07 ` Christoph Lameter
2006-10-19 20:37 ` Will Schmidt
2006-10-19 21:28 ` Christoph Lameter
2006-10-19 21:43 ` Will Schmidt
2006-10-19 22:00 ` Christoph Lameter
2006-10-19 21:39 ` Christoph Lameter
2006-10-19 20:38 ` Will Schmidt
2006-10-19 21:30 ` Christoph Lameter
2006-10-18 16:06 ` Christoph Lameter
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.64.0610161630430.8341@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=will_schmidt@vnet.ibm.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
all inboxes | Powered by JetHome®