Messages in this thread | | | Date | Wed, 07 Jul 1999 12:21:34 +0200 | From | Marc Mutz <> | Subject | Re: fs corruption caused by memory module |
| |
Steffen Evers wrote: > > I've experienced some problems with my new 128 MB DIMM memory module > that produced also a fs corruption: <snip> > After that I've tried other memory modules (64 MB and 128 MB) and there > was no problem at all. <snip> > A safe way to get a kernel panic was to mkfs with bad sector check under > 2.0.36 for a partion of 900MB. <snip>
Hi Steffen!
Have you tried to compile the kernel with the setup that caused the kernel panic? e2fsck and make {,b}zImage are real stress test for the memory subsystem and are often the applications that show you your hardware failures, although win et al. seem to run fine. I'd get a new DIMM from the vendor.
Marc
-- Marc Mutz <Marc@Mutz.com> http://marc.mutz.com/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS), 0x31748570 (DH)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |