From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: akpm@linux-foundation.org, penberg@cs.helsinki.fi, clameter@sgi.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: git-slub crashes on the t16p
Date: Thu, 10 Apr 2008 12:34:42 +0300 (EEST) [thread overview]
Message-ID: <lnun8CCD.1207820081.9463900.penberg@cs.helsinki.fi> (raw)
In-Reply-To: <20080410015958.bc2fd041.akpm@linux-foundation.org>
Hi,
On 4/10/2008, "Andrew Morton" <akpm@linux-foundation.org> wrote:
> It's the tree I pulled about 12 hours ago. Quite early in boot.
>
> crash: http://userweb.kernel.org/~akpm/p4105087.jpg
> config: http://userweb.kernel.org/~akpm/config-t61p.txt
> git-slub.patch: http://userweb.kernel.org/~akpm/mmotm/broken-out/git-slub.patch
>
> A t61p is a dual-core x86_64.
>
> I was testing with all of the -mm series up to and including git-slub.patch
> applied.
You have CONFIG_NUMA enabled, so we check for NULL in inc_slabs_node():
if (!NUMA_BUILD || n) {
atomic_long_inc(&n->nr_slabs);
atomic_long_add(objects, &n->total_objects);
I think I hit the same problem and it went away after make clean. Hmm...
Pekka
--
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:[~2008-04-10 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 8:59 Andrew Morton
2008-04-10 9:34 ` Pekka Enberg [this message]
2008-04-10 10:27 ` Pekka J Enberg
2008-04-10 15:52 ` Pekka Enberg
2008-04-10 16:35 ` Pekka Enberg
2008-04-10 17:24 ` Andrew Morton
2008-04-10 17:30 ` Christoph Lameter
2008-04-10 17:41 ` Pekka Enberg
2008-04-10 17:45 ` Pekka Enberg
2008-04-10 17:51 ` Christoph Lameter
2008-04-10 17:54 ` Christoph Lameter
2008-04-10 18:00 ` Pekka Enberg
2008-04-10 18:03 ` Andrew Morton
2008-04-10 17:10 ` 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=lnun8CCD.1207820081.9463900.penberg@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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