From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id E3ED3B7211 for ; Mon, 21 Nov 2011 12:25:55 +1100 (EST) Message-ID: <1321838742.13860.8.camel@pasglop> Subject: Re: 3.2.0-rc1 panic on PowerPC From: Benjamin Herrenschmidt To: Christian Kujau Date: Mon, 21 Nov 2011 12:25:42 +1100 In-Reply-To: References: <1321837101.13860.6.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev@lists.ozlabs.org, LKML List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Cheers, Ben. > Thanks, > Christian. > > > Looks like there's some kind of memory corruption happening. So far I > > haven't been able to get a good target at what could be causing it. >