From owner-freebsd-current@FreeBSD.ORG Tue May 13 11:56:00 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 4A07B37B401; Tue, 13 May 2003 11:56:00 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61E1E43F85; Tue, 13 May 2003 11:55:59 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h4DItoOn090829; Tue, 13 May 2003 14:55:50 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h4DItod0090826; Tue, 13 May 2003 14:55:50 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 13 May 2003 14:55:50 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Heiko Schaefer In-Reply-To: <20030513193830.Y14785@daneel.foundation.hs> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: re@FreeBSD.org cc: current@FreeBSD.org Subject: Re: 5.1-RELEASE TODO 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: Tue, 13 May 2003 18:56:00 -0000 On Tue, 13 May 2003, Heiko Schaefer wrote: > this might be the wrong way or place, but i want to state again (as i > already stated in my thread about data corruption), that in my opinion > it would be not a good idea to make a release of freebsd with the > GENERIC kernel config as it is. > > not having the options > > options DISABLE_PSE > options DISABLE_PG_G > > in the kernel config caused me data corruption which took hours of > testing (and bothering people on this list) to figure out. apparently > this problem is widespread and not only relevant to exotic fringe-case > systems. There's a lot of worry that this is simply masking the bug, as opposed to fixing it, as it's believed we already have workarounds for most of the Intel bugs being discussed. So we'd like to leave these out for now until it's clear that they fix the bug rather than masking it on some machines (and making it pop up on others). BTW, at least once instance of the "Intel bug" that has been proferred as a cause of these sorts of problems was resolved by recently driver fixes in if_bge. That said, we are actively discussing what, if any, workarounds are appropriate, including some alternative workarounds from the ones currently present. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories