From owner-freebsd-current@FreeBSD.ORG Fri May 9 22:41:23 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 A612637B401; Fri, 9 May 2003 22:41:23 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id E209643FA3; Fri, 9 May 2003 22:41:22 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx22-bradley.dialup.earthlink.net ([209.179.198.8] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19EN6n-0001xZ-00; Fri, 09 May 2003 22:41:22 -0700 Message-ID: <3EBC90B9.FE54107F@mindspring.com> Date: Fri, 09 May 2003 22:40:09 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Don Lewis References: <200305092100.h49L0TM7038764@gw.catspoiler.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46b9f7da6fb1c1b8443074d6af2cbc045350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@FreeBSD.org Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 05:41:23 -0000 Don Lewis wrote: > On 9 May, Mark Santcroos wrote: > > On Fri, May 09, 2003 at 08:33:35AM -0700, David O'Brien wrote: > >> 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. > > > > This thread is all about AMD. > > This problem afflicts both my PII and Athlon machines. Thanks for the report on the PII; I suspected it would have the same problem, but I had not been able to verify it. At a guess, I will say you have taken all the extraneous stuff you could out of your kernel, and are running with 256M+ of memory. 8-). -- Terry