Messages in this thread | | | Subject | Re: 3.2.0-rc1 panic on PowerPC | From | Benjamin Herrenschmidt <> | Date | Mon, 21 Nov 2011 12:51:41 +1100 |
| |
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.
| |