From: Nick Piggin <npiggin@suse.de> To: Sachin Sant <sachinp@in.ibm.com> Cc: Pekka J Enberg <penberg@cs.helsinki.fi>, Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org Subject: Re: [Powerpc/SLQB] Next June 06 : BUG during scsi initialization Date: Fri, 12 Jun 2009 09:42:13 +0200 [thread overview] Message-ID: <20090612074213.GA21070@wotan.suse.de> (raw) In-Reply-To: <4A31EB2A.9080003@in.ibm.com> On Fri, Jun 12, 2009 at 11:14:10AM +0530, Sachin Sant wrote: > Nick Piggin wrote: > >I can't really work it out. It seems to be the kmem_cache_cache which has > >a problem, but there have already been lots of caches created and even > >this samw cache_node already used right beforehand with no problem. > > > >Unless a CPU or node comes up or something right at this point or the > >caller is scheduled onto a different CPU... oopses seem to all > >have CPU#1, wheras boot CPU is probably #0 (these CPUs are node 0 > >and memory is only on node 1 and 2 where there are no CPUs if I read > >correctly). > > > >I still can't see the reason for the failure, but can you try this > >patch please and show dmesg? > I was able to boot yesterday's next (20090611) on this machine. Not sure Still with SLQB? With debug options turned on? > what changed(may be because of merge with linus tree), but i can no longer > recreate this issue with next 20090611. I was consistently able to > recreate the problem till June 10th next tree. I would guess some kind of memory corruption that by chance did not break the other allocators. Please let us know if you see any more crashes. Thanks for all your help.
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de> To: Sachin Sant <sachinp@in.ibm.com> Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Pekka J Enberg <penberg@cs.helsinki.fi>, linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org Subject: Re: [Powerpc/SLQB] Next June 06 : BUG during scsi initialization Date: Fri, 12 Jun 2009 09:42:13 +0200 [thread overview] Message-ID: <20090612074213.GA21070@wotan.suse.de> (raw) In-Reply-To: <4A31EB2A.9080003@in.ibm.com> On Fri, Jun 12, 2009 at 11:14:10AM +0530, Sachin Sant wrote: > Nick Piggin wrote: > >I can't really work it out. It seems to be the kmem_cache_cache which has > >a problem, but there have already been lots of caches created and even > >this samw cache_node already used right beforehand with no problem. > > > >Unless a CPU or node comes up or something right at this point or the > >caller is scheduled onto a different CPU... oopses seem to all > >have CPU#1, wheras boot CPU is probably #0 (these CPUs are node 0 > >and memory is only on node 1 and 2 where there are no CPUs if I read > >correctly). > > > >I still can't see the reason for the failure, but can you try this > >patch please and show dmesg? > I was able to boot yesterday's next (20090611) on this machine. Not sure Still with SLQB? With debug options turned on? > what changed(may be because of merge with linus tree), but i can no longer > recreate this issue with next 20090611. I was consistently able to > recreate the problem till June 10th next tree. I would guess some kind of memory corruption that by chance did not break the other allocators. Please let us know if you see any more crashes. Thanks for all your help.
next prev parent reply other threads:[~2009-06-12 7:42 UTC|newest] Thread overview: 61+ 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:04 ` Sachin Sant 2009-05-11 12:21 ` Matthew Wilcox 2009-05-11 12:21 ` Matthew Wilcox 2009-05-11 16:19 ` Sachin Sant 2009-05-11 16:19 ` Sachin Sant 2009-05-11 16:25 ` Matthew Wilcox 2009-05-11 16:25 ` Matthew Wilcox 2009-05-11 16:59 ` Sachin Sant 2009-05-12 4:57 ` Nick Piggin 2009-05-12 4:57 ` Nick Piggin 2009-05-12 5:56 ` Stephen Rothwell 2009-05-12 5:56 ` Stephen Rothwell 2009-05-12 5:59 ` Nick Piggin 2009-05-12 5:59 ` Nick Piggin 2009-05-12 6:03 ` Stephen Rothwell 2009-05-12 6:03 ` Stephen Rothwell 2009-05-12 6:52 ` Stephen Rothwell 2009-05-12 6:52 ` Stephen Rothwell 2009-05-12 6:56 ` Nick Piggin 2009-05-12 6:56 ` Nick Piggin 2009-05-14 8:30 ` Sachin Sant 2009-05-14 8:51 ` Pekka Enberg 2009-05-14 8:51 ` Pekka Enberg 2009-05-14 9:54 ` Sachin Sant 2009-05-14 9:54 ` Sachin Sant 2009-05-14 9:59 ` Pekka Enberg 2009-05-14 9:59 ` Pekka Enberg 2009-05-14 10:01 ` Pekka Enberg 2009-05-14 10:01 ` Pekka Enberg 2009-05-14 11:46 ` Sachin Sant 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-09 14:19 ` Nick Piggin 2009-06-12 5:44 ` Sachin Sant 2009-06-12 5:44 ` Sachin Sant 2009-06-12 7:42 ` Nick Piggin [this message] 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:21 ` Nick Piggin 2009-06-12 8:25 ` Pekka Enberg 2009-06-12 8:25 ` Pekka Enberg 2009-06-12 8:35 ` Stephen Rothwell 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=20090612074213.GA21070@wotan.suse.de \ --to=npiggin@suse.de \ --cc=linux-next@vger.kernel.org \ --cc=linuxppc-dev@ozlabs.org \ --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: linkBe 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.