[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080411085411.GA10181@elte.hu>
Date: Fri, 11 Apr 2008 10:54:11 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: linux-kernel@...r.kernel.org, Christoph Lameter <clameter@....com>,
Mel Gorman <mel@....ul.ie>, Nick Piggin <npiggin@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [bug] mm/slab.c boot crash in -git, "kernel BUG at
mm/slab.c:2103!"
* Pekka Enberg <penberg@...helsinki.fi> wrote:
> > > it to build on .25) but that didnt solve the problem either.
>
> On Fri, Apr 11, 2008 at 11:21 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> > As mentioned privately, I suspect it's the page allocator changes that
> > went into 2.6.24. Mel, Christoph, any ideas?
>
> So I'm thinking it's probably related to this patch:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=523b945855a1427000ffc707c610abe5947ae607
>
> As kmalloc_node() in setup_cpu_cache() returns NULL, it seems likely
> to be due to the use of GFP_THISNODE in cache_alloc_refill() when
> calling cache_grow() and that the semantics changed. No idea why page
> allocator would think your UMA "local node" has no memory though.
but ... as i said it in my report, this is a regression since v2.6.24 -
v2.6.24 (and a whole bunch of commits since then, i listed the IDs)
booted up fine. The commit ID you mention is: v2.6.23-4345-g523b945, way
earlier than the good commit IDs.
so this is a recent regression.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists