Re: data corruption with current (maybe sis chipset related?)

From: Don Lewis <truckman_at_FreeBSD.org>
Date: Fri, 9 May 2003 13:59:37 -0700 (PDT)
On  9 May, David O'Brien wrote:
> On Thu, May 08, 2003 at 05:38:44PM +0200, Mark Santcroos wrote:
>> On Thu, May 08, 2003 at 05:28:35PM +0200, Heiko Schaefer wrote:
>> > the thread i found in -current archives suggested that these flags work
>> > around an amd-specific issue. now you say that a p4-based machine also
>> > needs them to run stable.
>> 
>> No, it's the other way around. It's an Intel bug, which also went into AMD
>> products.
> 
> I'd love more details as I've *NEVER* found a problem running FreeBSD on
> Athlon systems nor has anyone else I know.  Please provide more detail
> about the Athlon issue.

I've seen it on my Athlon XP box with 1GB of ECC RAM.  If I ran "make
buildworld" a number of times in a row, it would barf on a corrupted
file in /usr/src.  A 16 byte chunk of a source file would be changed to
some sort of random garbage.  It was just the copy of the file that was
cached in RAM that was corrupted.  Rebooting the system would show that
the file was undamaged.  Adding the kernel options mentioned earlier in
this thread makes the machine run flawlessly.
Received on Fri May 09 2003 - 11:59:47 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:07 UTC