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