http://bugzilla.novell.com/show_bug.cgi?id=566288 http://bugzilla.novell.com/show_bug.cgi?id=566288#c21 --- Comment #21 from Robert Schweikert <rschweikert@novell.com> 2010-04-20 11:54:37 UTC --- (In reply to comment #19)
(In reply to comment #17)
Here is a trace from an oops that occurred with the debug kernel. The trace occurred while heavy I/O was taking place.
Apr 17 01:18:35 triumph kernel: [629085.891576] page:ffffea0001e53000 flags:0020000000000000 count:-775699968 mapcount:-43821 mapping:(null) index:46 Apr 17 01:18:35 triumph kernel: [629085.891594] Pid: 1122, comm: tar Tainted: P The struct page looks corrupted.
2.6.31.12-0.2-default #1
The kernel is not a -debug one as you claim to be (maybe you've just installed the debug package for the -default kernel and not the -debug kernel flavor?). Moreover you have some proprietary modules loaded so this dump isn't particularly interesting...
OK, missed that. what's interesting is that the dump occurred while I was gone and I was certain I had booted the debug kernel before I left. oh well, missed opportunity. Sorry about the incorrect claim.
Apr 17 01:20:01 triumph kernel: [629171.986844] BUG: Bad page state in process tar pfn:91492 Apr 17 01:20:01 triumph kernel: [629171.986865] page:ffffea0001fc7ff0 flags:0020000000000000 count:0 mapcount:0 mapping:000054d2d1c3c200 index:49f Again looks like corrupted struct page. Funnily enough, if you look how previous struct page was corrupted in hex, you'll see that pattern 0x54D3D1C3C200 was written to a part of the struct - upto one bit the same pattern that corrupted the mapping value in this struct page. So definitely something is scribbling over your memory => not too interesting unless you can reproduce it without tainted kernel.
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.