Date: Thu, 8 May 2003 17:38:44 +0200 From: Mark Santcroos <marks@ripe.net> To: Heiko Schaefer <hschaefer@fto.de> Cc: freebsd-current@freebsd.org Subject: Re: data corruption with current (maybe sis chipset related?) Message-ID: <20030508153844.GA1262@laptop.6bone.nl> In-Reply-To: <20030508172630.C79286@daneel.foundation.hs> References: <20030508142234.GA1359@laptop.6bone.nl> <3908.1052404777@critter.freebsd.dk> <20030508151810.GA72636@zibbi.icomtek.csir.co.za> <20030508172630.C79286@daneel.foundation.hs>
next in thread | previous in thread | raw e-mail | index | archive | help
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. It is also in the PIII, but because it is so subtle it was never triggered. > i am wondering more and more: why are these options not in GENERIC ?!? > ..if someone knows what he's doing he can always throw them out again. Because it is not (yet0 officially recognized. Terry mentioned that he explained it to Bosco, and that he had a patch to work around it in a different way. But that was from November, time has passed since then. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030508153844.GA1262>