From owner-freebsd-current Fri Nov 15 16: 1:37 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 3F14B37B401; Fri, 15 Nov 2002 16:01:36 -0800 (PST) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8EEF43E42; Fri, 15 Nov 2002 16:01:35 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0182.cvx22-bradley.dialup.earthlink.net ([209.179.198.182] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18CqP0-0005ge-00; Fri, 15 Nov 2002 16:01:35 -0800 Message-ID: <3DD58A8F.A402D461@mindspring.com> Date: Fri, 15 Nov 2002 16:00:15 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson Cc: John Baldwin , Wesley Morgan , freebsd-current@FreeBSD.org, Vallo Kallaste Subject: Re: DISABLE_PSE & DISABLE_PG_G still needed? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Robert Watson wrote: > On Fri, 15 Nov 2002, John Baldwin wrote: > > It only happens with P4's. I haven't seen it locally on a p4 test > > machine at work that I have built test releases on. Also, it would be > > nice to see if just adding one of the options fixed the problems. As > > for NOTES, those options should not be enabled in NOTES as they would > > defeat the purpose of LINT since they disable code. > > 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. The amount of RAM will also affect it. It can also happen on P3's and AMD K6's. It is a CPU bug related to the use of 4M pages. Bosko understands the problem (I have explained it to him under non-disclosure), and he has a patch which avoids it without really disclosing the problem, which I'm OK with. Using the patch cranks the amount of base memory required for a minimal FreeBSD up to 16M, and loads the kernel at 4M, instead of 1M. This avoids the problem on purpose that the older FreeBSD locore.s used to avoid by accident. The alternative is to take up to a 15% performance hit by not using 4M and global pages, or to revert the locore.s code so that it does not tickle the hardware bug. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message