From owner-freebsd-current@FreeBSD.ORG  Thu May  8 07:05:38 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 4608937B401; Thu,  8 May 2003 07:05:38 -0700 (PDT)
Received: from sauron.fto.de (p15106025.pureserver.info [217.160.140.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3892843FB1; Thu,  8 May 2003 07:05:37 -0700 (PDT)
	(envelope-from hschaefer@fto.de)
Received: from localhost (localhost.fto.de [127.0.0.1])
	by sauron.fto.de (Postfix) with ESMTP
	id DED2A25C0C1; Thu,  8 May 2003 16:05:35 +0200 (CEST)
Received: from sauron.fto.de ([127.0.0.1])
 by localhost (sauron [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 19663-02; Thu,  8 May 2003 16:05:34 +0200 (CEST)
Received: from giskard.foundation.hs (p5091A08C.dip.t-dialin.net
	[80.145.160.140])	by sauron.fto.de (Postfix) with ESMTP
	id 9806025C0C2; Thu,  8 May 2003 16:05:33 +0200 (CEST)
Received: from daneel.foundation.hs (daneel.foundation.hs [192.168.20.2])
	by giskard.foundation.hs (8.9.3/8.9.3) with ESMTP id QAA64043;
	Thu, 8 May 2003 16:05:29 +0200 (CEST)
	(envelope-from hschaefer@fto.de)
Date: Thu, 8 May 2003 16:05:29 +0200 (CEST)
From: Heiko Schaefer <hschaefer@fto.de>
X-X-Sender: heiko@daneel.foundation.hs
To: Mark Santcroos <marks@ripe.net>
In-Reply-To: <20030508111807.GB1390@laptop.6bone.nl>
Message-ID: <20030508155123.G78057@daneel.foundation.hs>
References: <20030506162410.M66653@daneel.foundation.hs>
	<20030508111807.GB1390@laptop.6bone.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at fto.de
cc: alc@freebsd.org
cc: Poul-Henning Kamp <phk@phk.freebsd.dk>
cc: freebsd-current@freebsd.org
cc: Robert Watson <rwatson@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: Thu, 08 May 2003 14:05:38 -0000

> On Tue, May 06, 2003 at 07:16:32PM +0200, Mark Santcroos wrote:
> > 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

ok. i have done my copying and checksumming orgy with these options in the
kernel - and it seems that i do not get any corruption anymore.
i will re-run my test once again now, just to be safe.

after that: does it make sense to single out which of the two options is
the relevant one ?

i'm also clueless what exactly these options do, and what exactly we've
ruled out now. could the lack of data-corruption just be some side-effect?

thanks, regards,

Heiko