Message-ID: <000701c16912$cf1915a0$0c01a8c0@vaio>
From: "Robert Lowery" <cangela@bigpond.net.au>
To: <akpm@zip.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Assertion failure wth ext3 on standard Redhat 7.2 kernel
Date: Fri, 9 Nov 2001 22:36:44 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

Hi Andrew,


>ext3 downloads are currently running at 1,200 per day plus
>an unknown number of Red Hat users, and you're the first to report
>this one. So it's going to be something odd. It _could_ be bad
>hardware, but if it's always failing in the same way, that sounds
>unlikely.

I too thought bad hardware.  I will try removing the extra 64M I added
recently and see if it still happens.


>Could you please force a `fsck' against the fs, let us know the
>outcome?
After a crash I say Y (within 5 seconds) on reboot to run an fsck and there
are usually corrupted files from what I was doing when it crashed.  Eg I was
running rpm -Uvh kernel-sources... and some files in /usr/src/linux... were
corrupted.

>Also, a ksymoops trace of the oops output would be most useful.

How do I do this when the box has crashed?  I can manually write down the
oops, but then what do I do?  Can I manually look up System.map to get what
you need?


>It looks like memory corruption of some form - a structure
>member has an impossible value. Are you using any less-than-mainstream
>device drivers in that box?
I agree.  Everything is pointing to the new memory, even though I
successfully ran memtest86 for 10 hours.

Thanks

-Robert


-
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/