From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linuxppc-dev@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.2.0-rc1 panic on PowerPC
Date: Mon, 21 Nov 2011 12:51:41 +1100 [thread overview]
Message-ID: <1321840301.13860.9.camel@pasglop> (raw)
In-Reply-To: <1321838742.13860.8.camel@pasglop>
On Mon, 2011-11-21 at 12:25 +1100, Benjamin Herrenschmidt wrote:
> On Sun, 2011-11-20 at 17:17 -0800, Christian Kujau wrote:
> > On Mon, 21 Nov 2011 at 11:58, Benjamin Herrenschmidt wrote:
> > > I've seen something similar with 3.2-rc2 at cfcfc9ec, unfortunately I
> > > couldn't capture the oops log at the time.
> >
> > It just happened again today, after heavy CPU & IO load (rsyncing from/to
> > external disks on dm-crypt). This time the oops was printed on the screen
> > but nothing on netconsole:
> >
> > http://nerdbynature.de/bits/3.2.0-rc1/oops/oops3m.JPG
> >
> > It looks like the oops I reported earlier (oops2m.JPG) so I doubt it's a
> > random corruption due to hardware issues...?
>
> Yeah it's starting to look like a pattern. Your latest oops looks a lot
> like the one I had (though it was with tg3 on the g5), ie, vfs_read ->
> driver -> allocator -> crash.
>
> > Any debug or boot options to set in my next kernel build?
>
> Well, you can turn everything on see whether that makes any difference
> or finds something a bit more precisely
BTW. SLUB or SLAB ? Mine was SLUB with SLUB_DEBUG enabled (tho the debug
didn't seem to catch anything).
Cheers,
Ben.
next prev parent reply other threads:[~2011-11-21 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 8:44 3.2.0-rc1 panic on PowerPC Christian Kujau
2011-11-20 23:31 ` Christian Kujau
2011-11-21 0:58 ` Benjamin Herrenschmidt
2011-11-21 1:17 ` Christian Kujau
2011-11-21 1:25 ` Benjamin Herrenschmidt
2011-11-21 1:51 ` Benjamin Herrenschmidt [this message]
2011-11-21 2:03 ` Christian Kujau
2011-11-21 8:08 ` Markus Trippelsdorf
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=1321840301.13860.9.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
/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