File corruption: how to find the guilty?

[Beau James]

--> > 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.
--> 
--> My dear Doug,
--> 
--> I am happy to say you're right!
--> Since I have a new Pentium machine, I have been bothered with many
--> applications blowing out all
--> the time. When recompiling the kernel, internal errors stopped
--> the gcc program. I had segmentation faults.
--> 
--> Reading your mail I removed one RAM memory. Since then it works fine ---
--> actually gcc blown out once since. 
--> 
--> Do you know of a way to anticipate the problem and make a relevant hardware
--> set of tests?

Gcc is a good test, but a lousy diagnostic.

Use parity or ECC memory if you care about system integrity.
It doesn't cost significantly more.

Beau

+-------------------------+---------------------+---------------------------+
+      ||        ||       + Cisco Systems, Inc. + Beau James                +
+      ||        ||       + 170 West Tasman Dr. + Mgr, xDSL Switch S/W      +
+     ||||      ||||      + San Jose, CA   95134+ Phone:     (408) 526-8328 +
+ ..:||||||:..:||||||:..  +                     + FAX:       (408) 527-0495 +
+   Cisco Systems Inc.    +                     + Email:   bjames at cisco.com +
+-------------------------+---------------------+---------------------------+


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