Messages in this thread | | | From | Maciej Sołtysiak <> | Subject | Re: 2.6.21.14 NFS related oops | Date | Sat, 16 Jun 2007 11:26:09 +0200 |
| |
>> ======================= >> Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a >> 8b >> 4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 <18> 83 c4 1c >> c3 >> 89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: [<f0a93c94>] >> rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec > > At a first guess, it looks as though something has scribbled over your > credential. Have you tried running this kernel with slab debugging > enabled?
I'm running 2.6.21.5 now with slab debugging on, here's what I got about slab corruption:
Slab corruption: skbuff_head_cache start=ef287b78, len=164 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<c031710c>](kfree_skbmem+0x3c/0x90) 090: 6b 6b 6b 6b 6b 63 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Single bit error detected. Probably bad RAM. Run memtest86+ or a similar memory test tool. Prev obj: start=ef287ac8, len=164 Redzone: 0x170fc2a5/0x170fc2a5. Last user: [<c031798b>](__alloc_skb+0x2b/0x100) 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 010: 00 00 00 00 e0 71 e6 ef 00 00 00 00 00 00 00 00 Next obj: start=ef287c28, len=164 Redzone: 0x170fc2a5/0x170fc2a5. Last user: [<c031798b>](__alloc_skb+0x2b/0x100) 000: 84 d0 85 c5 84 d0 85 c5 04 d0 85 c5 2c 0a 73 46 010: 6f cd 09 00 00 00 00 00 01 00 00 00 08 e5 72 ee
How probable is that it is really a bad memory issue? Does this report say anything about which RAM chip I should investigate/replace ? I have 1x512MB+1x256MB
Best Regards, Maciej
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |