From: Nick Piggin <npiggin@suse.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
cl@linux-foundation.org, heiko.carstens@de.ibm.com,
mingo@elte.hu, sachinp@in.ibm.com
Subject: Re: [RFC/PATCH] SLQB: Mark the allocator as broken PowerPC and S390
Date: Thu, 17 Sep 2009 20:28:42 +0200 [thread overview]
Message-ID: <20090917182842.GS18404@wotan.suse.de> (raw)
In-Reply-To: <20090917181831.GA714@csn.ul.ie>
On Thu, Sep 17, 2009 at 07:18:32PM +0100, Mel Gorman wrote:
> > Ahh... it's pretty lame of me. Sachin has been a willing tester :(
> > I have spent quite a few hours looking at it but I never found
> > many good leads. Much appreciated if you can make more progress on
> > it.
>
> Nothing much so far. I've reproduced the problem based on 2.6.31 and slqb-core
> from Pekka's tree but not a whole pile else. I don't know SLQB at all so the
> investigation is fuzzy. It appears to initialise SLQB ok but crashes later when
> setting up SCSI. Not 100% sure what the triggering event is but it might be
> userspace starting up and other CPUs get involved, possibly corrupting lists.
>
> This machine has two CPUs (0, 1) and two nodes with actual memory (2,3).
> After applying a patch to kmem_cache_create, I see in the console
>
> MEL::Creating cache pgd_cache CPU 0 Node 0
> MEL::Creating cache pmd_cache CPU 0 Node 0
> MEL::Creating cache pid_namespace CPU 0 Node 0
> MEL::Creating cache shmem_inode_cache CPU 0 Node 0
> MEL::Creating cache scsi_data_buffer CPU 1 Node 0
>
> It crashes at this point during creation before the struct kmem_cache has
> been allocated from kmem_cache_cache. Note it's kmem_cache_cache we are
> failing to allocate from, not scsi_data_buffer.
Yes, it's crashing in kmem_cache_create, when trying to allocate from
kmem_cache_cache.
I didn't get much further. I had thought something must be NULL or
not set up correctly in kmem_cache_cache, but I didn't work out what.
If you can identify the precondition which cases the crash (or even
just have a static counter of the number of caches created, to trigger
at the crashing cache create), then perhaps you can dump some more
details of the kmem_cache_cache.
Thanks,
Nick
next prev parent reply other threads:[~2009-09-17 18:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 6:37 [RFC/PATCH] SLQB: Mark the allocator as broken PowerPC and S390 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
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 [this message]
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=20090917182842.GS18404@wotan.suse.de \
--to=npiggin@suse.de \
--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=penberg@cs.helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.