From owner-freebsd-current@FreeBSD.ORG  Tue May  6 12:15:11 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 789CF37B401
	for <current@freebsd.org>; Tue,  6 May 2003 12:15:11 -0700 (PDT)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 797F743FB1
	for <current@freebsd.org>; Tue,  6 May 2003 12:15:10 -0700 (PDT)
	(envelope-from marks@ripe.net)
Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239])
	by birch.ripe.net (8.12.9/8.11.6) with SMTP id h46JF9Ss020139;
	Tue, 6 May 2003 21:15:09 +0200
Received: (nullmailer pid 6259 invoked by uid 1000);
	Tue, 06 May 2003 17:16:33 -0000
Date: Tue, 6 May 2003 19:16:32 +0200
From: Mark Santcroos <marks@ripe.net>
To: Heiko Schaefer <hschaefer@fto.de>
Message-ID: <20030506171632.GA767@laptop.6bone.nl>
References: <20030506162410.M66653@daneel.foundation.hs>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030506162410.M66653@daneel.foundation.hs>
User-Agent: Mutt/1.4.1i
X-Handles: MS6-6BONE, MS18417-RIPE
cc: 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: Tue, 06 May 2003 19:15:11 -0000

On Tue, May 06, 2003 at 04:41:30PM +0200, Heiko Schaefer wrote:
> does anyone know of any (freebsd-current) issues that might be causing
> this - or have any idea on how i can further rule out anything of this
> kind ?

Try this in your kernel config:

options		DISABLE_PSE
options		DISABLE_PG_G

-- 
Mark Santcroos                    RIPE Network Coordination Centre
http://www.ripe.net/home/mark/    New Projects Group/TTM