Date: Fri, 9 May 2003 08:33:35 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Mark Santcroos <marks@ripe.net> Cc: Heiko Schaefer <hschaefer@fto.de> Subject: Re: data corruption with current (maybe sis chipset related?) Message-ID: <20030509153335.GA61844@dragon.nuxi.com> In-Reply-To: <20030508153844.GA1262@laptop.6bone.nl> References: <20030508142234.GA1359@laptop.6bone.nl> <3908.1052404777@critter.freebsd.dk> <20030508151810.GA72636@zibbi.icomtek.csir.co.za> <20030508172630.C79286@daneel.foundation.hs> <20030508153844.GA1262@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030509153335.GA61844>