From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ud10.udmedia.de (ud10.udmedia.de [194.117.254.50]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ud10.udmedia.de", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id C9409B720D for ; Mon, 21 Nov 2011 19:15:37 +1100 (EST) Date: Mon, 21 Nov 2011 09:08:49 +0100 From: Markus Trippelsdorf To: Benjamin Herrenschmidt Subject: Re: 3.2.0-rc1 panic on PowerPC Message-ID: <20111121080849.GC1625@x4.trippels.de> References: <1321837101.13860.6.camel@pasglop> <1321838742.13860.8.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1321838742.13860.8.camel@pasglop> Cc: Christian Kujau , 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 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. I might be seeing a similar issue on x86_64. See: http://thread.gmane.org/gmane.linux.kernel.mm/70254 -- Markus