Date: Thu, 8 May 2003 16:22:35 +0200 From: Mark Santcroos <marks@ripe.net> To: Heiko Schaefer <hschaefer@fto.de> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: data corruption with current (maybe sis chipset related?) Message-ID: <20030508142234.GA1359@laptop.6bone.nl> In-Reply-To: <20030508155123.G78057@daneel.foundation.hs> References: <20030506162410.M66653@daneel.foundation.hs> <20030506171632.GA767@laptop.6bone.nl> <20030508111807.GB1390@laptop.6bone.nl> <20030508155123.G78057@daneel.foundation.hs>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030508142234.GA1359>