Date: Fri, 9 May 2003 13:59:37 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: hschaefer@fto.de Subject: Re: data corruption with current (maybe sis chipset related?) Message-ID: <200305092059.h49KxbM7038755@gw.catspoiler.org> In-Reply-To: <20030509153335.GA61844@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305092059.h49KxbM7038755>