linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	mingo@elte.hu, tglx@linutronix.de, apw@shadowen.org,
	randy.dunlap@oracle.com, linux-mm@kvack.org
Subject: Re: [BUG] regression from 2.6.24-rc8-mm1 and 2.6.24-mm1 kernel panic while bootup
Date: Tue, 05 Feb 2008 18:00:25 +0530	[thread overview]
Message-ID: <47A856E1.4040703@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080205002544.264a9484.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Tue, 05 Feb 2008 13:48:17 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
[snip]

> argh, I'd forgotten about that.  You bisected it down to a clearly-innocent
> patch and none of the mm developers appeared interested.
> 
> Oh well, it'll probably be in mainline tomorrow.  That should get it
> fixed.

We've tracked this down to a problem where the nodeid might be invalid. Kamalesh
is investigating problem. We suspect we are doing a kmalloc_node with an invalid
nodeid.

We see

cpu with no node 2, num_online_nodes 1
cpu with no node 3, num_online_nodes 1

in the bootlog. Kamalesh verified that the problem exists with both slub and slab.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

--
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:[~2008-02-05 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47A81BC9.5060600@linux.vnet.ibm.com>
2008-02-05  8:25 ` Andrew Morton
2008-02-05 12:30   ` Balbir Singh [this message]

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=47A856E1.4040703@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.com \
    --cc=tglx@linutronix.de \
    /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