File corruption: how to find the guilty?

[Ph. MICHEL]

Doug Ledford schrieb:

> Stephane Bortzmeyer wrote:
> >
> > I have a Linux box which shows random corruption of files. Example: all Perl
> > scripts suddenly die with "segmentation fault". Reinstalling the same Perl
> > package cures it. Two days ago, /etc/resolv.conf became corrupted : strange
> > characters were in it.

> > I run Linux 2.0.35 (Debian distribution 2.0), patched for the Adaptec driver

> > 5.1.2. Here is the configuration:

>
> It's memory corruption.  I've seen this float through this list or that about
> 30 different times in the past.  Not once has it ever been a kernel or driver
> issue.  In *every* case it has been either RAM, cache, or CPU.  Check the CPU
> fan, check the cache (if it isn't part of the CPU) and check your RAM.

I think I had a similar problem on my old machine and a CD-Rom drive, which brings
me constantly some errors and corrupted files. As a changed the main board and the
RAM, the CD-Rom runs correctly. So it is probably a material problem, but not
necessary the mainboard or CPU or RAM, because the same CD-Rom and the same old
board with the same old RAM worked perfectly together, if I use an 1505 instead of
a 2940.

I would propose to install and test some newer driver (actual 5.1.6).


--
Philippe MICHEL
- phm at tpgnet.net
- himmelsbach at baden-online.de



To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message