Messages in this thread | | | Date | Sat, 5 Jan 2002 15:31:13 -0800 (PST) | From | Eric <> | Subject | Re: 2.4.17 oops - ext2/ext3 fs corruption (?) |
| |
On Sat, 5 Jan 2002, Andrew Morton wrote:
> Eric wrote: > > > > I seem to be having a reoccurring problem with my Red Hat 7.2 system > > running kernel 2.4.17. Four times now, I have seen the kernel generate an > > oops. After the oops, I find that one of file systems is no longer sane. > > The effect that I see is a Segmentation Fault when things like ls or du > > some directory (the directory is never the same). Also, when the system > > is going down for a reboot, it is unable to umount the file system. The > > umount command returns a "bad lseek" error. > > Everything here points at failing hardware. Probably memory errors. > People say that memtest86 is good at detecting these things. Another > way to verify this is to move the same setup onto a different computer...
I ran memtest86 on the system and let it complete 4 passes before I stopped it. It found no errors. Unfortunately, I do not have another system available to test this on. Are there any other diagnostics I can run to determine if this is truly a hardware problem?
Thanks,
Eric
- 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/
| |