From owner-freebsd-current Sat Nov 16 1:58:58 2002 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 3C37137B401; Sat, 16 Nov 2002 01:58:57 -0800 (PST) Received: from MX1.estpak.ee (mta1.mail.neti.ee [194.126.101.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id A244843E4A; Sat, 16 Nov 2002 01:58:56 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from tiiu.internal (80-235-42-246-dsl.mus.estpak.ee [80.235.42.246]) by MX1.estpak.ee (Postfix) with ESMTP id 4F5FD8889C; Sat, 16 Nov 2002 11:58:01 +0200 (EET) Received: from tiiu.internal (localhost [127.0.0.1]) by tiiu.internal (8.12.6/8.12.6) with ESMTP id gAG9wsXZ001120; Sat, 16 Nov 2002 11:58:54 +0200 (EET) (envelope-from vallo@tiiu.internal) Received: (from vallo@localhost) by tiiu.internal (8.12.6/8.12.6/Submit) id gAG9wrx9001119; Sat, 16 Nov 2002 11:58:53 +0200 (EET) (envelope-from vallo) Date: Sat, 16 Nov 2002 11:58:53 +0200 From: Vallo Kallaste To: Robert Watson Cc: John Baldwin , Wesley Morgan , freebsd-current@FreeBSD.org, Terry Lambert Subject: Re: DISABLE_PSE & DISABLE_PG_G still needed? Message-ID: <20021116095853.GA1070@tiiu.internal> Reply-To: kalts@estpak.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 15, 2002 at 11:45:16AM -0500, Robert Watson wrote: > Does this apply generally to all P4's, or just a subset? If all, it may > be we want to add a P4-workaround to GENERIC so that P4's work better ouf > of the box. If it's a select few, I wonder if there's some way to test > for the problem early in the boot... > > One of the recurring themes here has (a) been P4 processors, and (b) been > a fear that because of timing changes introduced by the DISABLE_FOO flags, > the real bug is still there, but less visible in the tests people are > running. Certainly doesn't happen on my P3-500 SMP system. I've finished two buildworlds without any problems. As everyone seems to think that it happens only on P4's, I'm not going to try it on old P2-400. That's all I can provide, happens reliably (for months now) on my P4 and doesn't happen with P3. 5.0-RELEASE definitely needs a fix. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message