![]() | |||||||||||||
Messages in this thread |
On Mon, 6 Mar 2006 11:16:13 -0800 (PST) Linus Torvalds <torvalds@osdl.org> wrote: > On Thu, 2 Mar 2006, Paolo Ornati wrote: > > > > Something is happened again here! > > I think you have bad ram. > > > Slab corruption: start=ffff81000d0ffb30, len=104 > > Redzone: 0x5a2cf071/0x5a2cf071. > > Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39) > > 000: 6b 6b 6b 2b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b My suspect was that the failing addr was the same one I had already seen some time ago with memtest86+ and that was (apparently?) fixed by disabling "bank interleaving" in the BIOS. But now that I've rechecked... it was a different address: 76.1 MB -- 04c0 37fc TEST 6 good FF FF FF FD bad F7 FF FF FD The one detected with DEBUG_SLAB is at 208.99 MB (so both problems are in my first 256MB memory module) but I'm unable to reproduce it with memtest86+... I wonder if these two are related in some way... or maybe it's just a weak memory module ;) -- Paolo Ornati Linux 2.6.16-rc5-g501f74f2 on x86_64 - 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/ | ||||||||||||
| Last update: 2006-03-07 08:54 [from the cache] ©2003-2008 | |||||||||||||