From owner-freebsd-current@FreeBSD.ORG Fri May 9 08:33:59 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CA4E37B401 for ; Fri, 9 May 2003 08:33:59 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB07443F3F for ; Fri, 9 May 2003 08:33:58 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h49FXbm2062164; Fri, 9 May 2003 08:33:42 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h49FXZ1A062163; Fri, 9 May 2003 08:33:35 -0700 (PDT) Date: Fri, 9 May 2003 08:33:35 -0700 From: "David O'Brien" To: Mark Santcroos Message-ID: <20030509153335.GA61844@dragon.nuxi.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030508153844.GA1262@laptop.6bone.nl> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: Heiko Schaefer Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 15:33:59 -0000 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)