From owner-freebsd-current@FreeBSD.ORG  Fri May  9 14:00:37 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 49A5037B401
	for <freebsd-current@FreeBSD.org>;
	Fri,  9 May 2003 14:00:37 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9D05B43F75
	for <freebsd-current@FreeBSD.org>;
	Fri,  9 May 2003 14:00:36 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h49L0TM7038764;
	Fri, 9 May 2003 14:00:33 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200305092100.h49L0TM7038764@gw.catspoiler.org>
Date: Fri, 9 May 2003 14:00:29 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: marks@ripe.net
In-Reply-To: <20030509200917.GB631@laptop.6bone.nl>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 May 2003 21:00:37 -0000

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.