From owner-freebsd-current@FreeBSD.ORG Thu May 8 07:22:37 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 81DEA37B401; Thu, 8 May 2003 07:22:37 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC5F43FD7; Thu, 8 May 2003 07:22:36 -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 h48EMZqo019532; Thu, 8 May 2003 16:22:35 +0200 Received: (nullmailer pid 1399 invoked by uid 1000); Thu, 08 May 2003 14:22:35 -0000 Date: Thu, 8 May 2003 16:22:35 +0200 From: Mark Santcroos To: Heiko Schaefer Message-ID: <20030508142234.GA1359@laptop.6bone.nl> References: <20030506162410.M66653@daneel.foundation.hs> <20030506171632.GA767@laptop.6bone.nl> <20030508111807.GB1390@laptop.6bone.nl> <20030508155123.G78057@daneel.foundation.hs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030508155123.G78057@daneel.foundation.hs> User-Agent: Mutt/1.4.1i X-Handles: MS6-6BONE, MS18417-RIPE cc: alc@freebsd.org cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: Robert Watson 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: Thu, 08 May 2003 14:22:37 -0000 On Thu, May 08, 2003 at 04:05:29PM +0200, Heiko Schaefer wrote: > > 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 ? No. > 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? They prevent the usage of 4M pages. It's a CPU bug that will cause data corruption if enabled. Terry Lambert (at least) knows the details. Search the -current archives for the discussions about it. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM