From: Christoph Lameter <clameter@sgi.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@skynet.ie>,
linux-kernel@vger.kernel.org,
Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [BUG] 2.6.23-rc3-mm1 kernel BUG at mm/page_alloc.c:2876!
Date: Thu, 23 Aug 2007 13:05:22 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708231303050.14720@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <46CDC11E.2010008@linux.vnet.ibm.com>
On Thu, 23 Aug 2007, Kamalesh Babulal wrote:
> After applying the patch, the call trace is gone but the kernel bug
> is still hit
Yes that is what we expected. We need more information to figure out why
the kmalloc_node fails there. It should walk through all nodes to find
memory.
I see that you have 4 cpus and 16 nodes. How are the cpus assigned to
nodes? If a cpu would be assigned to a nonexisting node then this could be
the result.
Could you post the full boot log?
--
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>
next prev parent reply other threads:[~2007-08-23 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46CC9A7A.2030404@linux.vnet.ibm.com>
2007-08-22 20:48 ` Andrew Morton
2007-08-22 20:50 ` Andrew Morton
2007-08-23 13:07 ` Mel Gorman
2007-08-23 17:17 ` Kamalesh Babulal
2007-08-23 20:05 ` Christoph Lameter [this message]
2007-08-24 6:15 ` Kamalesh Babulal
2007-08-24 8:58 ` Mel Gorman
2007-08-24 16:54 ` Christoph Lameter
2007-08-22 21:09 ` 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.0708231303050.14720@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
/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