From: Nick Piggin <npiggin@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Sachin Sant <sachinp@in.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Next May 11 : BUG during scsi initialization
Date: Tue, 12 May 2009 06:57:16 +0200 [thread overview]
Message-ID: <20090512045716.GC32535@wotan.suse.de> (raw)
In-Reply-To: <20090511122135.GC8112@parisc-linux.org>
On Mon, May 11, 2009 at 06:21:35AM -0600, Matthew Wilcox wrote:
> On Mon, May 11, 2009 at 05:34:07PM +0530, Sachin Sant wrote:
> > Matthew Wilcox wrote:
> >> On Mon, May 11, 2009 at 05:16:10PM +0530, Sachin Sant wrote:
> >>
> >>> Today's Next tree failed to boot on a Power6 box with following BUG :
> >>
> >> This doesn't actually appear to be a SCSI bug ... it looks like SCSI tried
> >> to allocate memory and things went wrong in the memory allocator:
> >>
> >> [c0000000c7d038b0] [c0000000005d67d8] ._spin_lock+0x10/0x24
> >> [c0000000c7d03920] [c00000000013fbdc] .__slab_alloc_page+0x344/0x3cc
> >> [c0000000c7d039e0] [c000000000141168] .kmem_cache_alloc+0x13c/0x21c
> >> [c0000000c7d03aa0] [c000000000141b04] .kmem_cache_create+0x294/0x2a8
> >> [c0000000c7d03b90] [d000000000ea14cc] .scsi_init_queue+0x38/0x170 [scsi_mod]
> >>
> >> Which memory allocator did you have selected (SLAB, SLUB, SLOB, SLQB)?
> >>
> > Default one. SLQB
> >
> > CONFIG_SLQB_ALLOCATOR=y
> > CONFIG_SLQB=y
> >
> > Page size is 64K with Config DEBUG_PAGEALLOC set.
> >
> > CONFIG_PPC_HAS_HASH_64K=y
> > CONFIG_PPC_64K_PAGES=y
> > CONFIG_DEBUG_PAGEALLOC=y
>
> Hm. We've seen some similar problems at Intel while doing database
> performance tests with SLQB. Any ideas, Nick?
Hmm, I think (hope) your problems were fixed with the recent memory
coruption bug fix for SLQB. (if not, let me know)
This one possibly looks like a problem with remote memory allocation
or memory hotplug or something like that. I'll do a bit of code
review....
next prev parent reply other threads:[~2009-05-12 4:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 6:14 linux-next: Tree for May 11 Stephen Rothwell
2009-05-11 11:46 ` Next May 11 : BUG during scsi initialization Sachin Sant
2009-05-11 11:52 ` Matthew Wilcox
2009-05-11 12:04 ` Sachin Sant
2009-05-11 12:21 ` Matthew Wilcox
2009-05-11 16:19 ` Sachin Sant
2009-05-11 16:25 ` Matthew Wilcox
2009-05-11 16:59 ` Sachin Sant
2009-05-12 4:57 ` Nick Piggin [this message]
2009-05-12 5:56 ` Stephen Rothwell
2009-05-12 5:59 ` Nick Piggin
2009-05-12 6:03 ` Stephen Rothwell
2009-05-12 6:52 ` Stephen Rothwell
2009-05-12 6:56 ` Nick Piggin
2009-05-14 8:30 ` Sachin Sant
2009-05-14 8:51 ` Pekka Enberg
2009-05-14 9:54 ` Sachin Sant
2009-05-14 9:59 ` Pekka Enberg
2009-05-14 10:01 ` Pekka Enberg
2009-05-14 11:46 ` Sachin Sant
2009-06-05 12:04 ` [Powerpc/SLQB] Next June 06 " Sachin Sant
2009-06-07 8:06 ` Pekka J Enberg
2009-06-08 12:12 ` Sachin Sant
2009-06-09 14:19 ` Nick Piggin
2009-06-12 5:44 ` Sachin Sant
2009-06-12 7:42 ` Nick Piggin
2009-06-12 8:08 ` Sachin Sant
2009-06-12 8:21 ` Nick Piggin
2009-06-12 8:25 ` Pekka Enberg
2009-06-12 8:35 ` Stephen Rothwell
2009-06-12 8:38 ` Pekka Enberg
2009-05-11 16:32 ` [PATCH -next] kvm: fix build error: add missing semi-colon Randy Dunlap
2009-05-12 8:31 ` Avi Kivity
2009-05-11 16:36 ` [PATCH -next] soc_camera: depends on I2C Randy Dunlap
2009-05-11 17:53 ` Guennadi Liakhovetski
2009-05-11 16:37 ` [PATCH -next] v4l2: handle unregister for non-I2C builds Randy Dunlap
2009-05-22 5:48 ` Paul Mundt
2009-05-22 7:55 ` Stephen Rothwell
2009-05-22 15:57 ` Randy Dunlap
2009-05-26 17:31 ` Mauro Carvalho Chehab
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=20090512045716.GC32535@wotan.suse.de \
--to=npiggin@suse.de \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthew@wil.cx \
--cc=penberg@cs.helsinki.fi \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).