From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
cl@linux-foundation.org, heiko.carstens@de.ibm.com,
mingo@elte.hu, npiggin@suse.de, sachinp@in.ibm.com
Subject: Re: [RFC/PATCH] SLQB: Mark the allocator as broken PowerPC and S390
Date: Thu, 17 Sep 2009 13:29:24 +0300 [thread overview]
Message-ID: <1253183365.4975.20.camel@penberg-laptop> (raw)
In-Reply-To: <20090917100841.GF13002@csn.ul.ie>
Hi Mel,
On Wed, Sep 16, 2009 at 09:37:39AM +0300, Pekka Enberg wrote:
> > The SLQB allocator is known to be broken on certain PowerPC and S390
> > configurations. Disable the allocator in Kconfig for those architectures
> > until the issues are resolved.
>
> Can the issues be summarised?
It's a boot time crash during module load:
http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg33092.html
AFAICT, it's related to a memoryless node 0. Nick suggested it could be
a latent bug in the kernel that's triggered by SLQB.
On Thu, 2009-09-17 at 11:08 +0100, Mel Gorman wrote:
> The danger is if SLQB is being silently disabled, it'll never be noticed
> or debugged :/
Maybe, but that's not an excuse to push something that's known to break.
The other alternative is to skip this release cycle but I'm not sure
what we'd gain with that. Nick already stated in private that he'll try
to arrange for some time with ppc machines to debug the thing and we
hope to be able to fix it by 2.6.32 final.
Btw, the code is in slqb/core branch of slab.git in case someone wants
to take a stab at fixing the bug.
Pekka
next prev parent reply other threads:[~2009-09-17 10:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 6:37 Pekka Enberg
2009-09-16 6:55 ` David Rientjes
2009-09-16 7:01 ` Pekka Enberg
2009-09-16 8:04 ` Heiko Carstens
2009-09-17 10:08 ` Mel Gorman
2009-09-17 10:29 ` Pekka Enberg [this message]
2009-09-17 10:57 ` Mel Gorman
2009-09-17 11:13 ` Pekka Enberg
2009-09-17 11:18 ` Mel Gorman
2009-09-17 11:23 ` Pekka Enberg
2009-09-17 11:41 ` Nick Piggin
2009-09-17 18:18 ` Mel Gorman
2009-09-17 18:28 ` Nick Piggin
2009-09-17 18:38 ` Christoph Lameter
2009-09-17 18:51 ` Nick Piggin
2009-09-18 15:56 ` Mel Gorman
2009-09-17 11:23 ` Sachin Sant
2009-09-17 11:38 ` Nick Piggin
2009-09-17 11:43 ` Pekka Enberg
2009-09-17 11:52 ` Nick Piggin
2009-09-17 11:55 ` Pekka Enberg
2009-09-17 12:12 ` Heiko Carstens
2009-09-17 12:16 ` Pekka Enberg
2009-09-17 12:21 ` Heiko Carstens
2009-09-17 12:36 ` Nick Piggin
2009-09-17 12:42 ` Pekka Enberg
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=1253183365.4975.20.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=sachinp@in.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®