From owner-freebsd-current Sat Nov 23 2:45:35 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 4E7F037B401; Sat, 23 Nov 2002 02:45:34 -0800 (PST) Received: from MX1.estpak.ee (mta1.mail.neti.ee [194.126.101.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBAED43E88; Sat, 23 Nov 2002 02:45:32 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from tiiu.internal (80-235-37-60-dsl.mus.estpak.ee [80.235.37.60]) by MX1.estpak.ee (Postfix) with ESMTP id 3456E888B2; Sat, 23 Nov 2002 12:44:31 +0200 (EET) Received: from tiiu.internal (localhost [127.0.0.1]) by tiiu.internal (8.12.6/8.12.6) with ESMTP id gANAjPBr001335; Sat, 23 Nov 2002 12:45:25 +0200 (EET) (envelope-from vallo@tiiu.internal) Received: (from vallo@localhost) by tiiu.internal (8.12.6/8.12.6/Submit) id gANAjPiu001334; Sat, 23 Nov 2002 12:45:25 +0200 (EET) (envelope-from vallo) Date: Sat, 23 Nov 2002 12:45:24 +0200 From: Vallo Kallaste To: Terry Lambert Cc: John Baldwin , current@FreeBSD.org, Scott Sipe Subject: Re: DP2 Fatal Trap Message-ID: <20021123104524.GA1264@tiiu.internal> Reply-To: kalts@estpak.ee References: <3DDD7C44.84C0D242@mindspring.com> <20021122162443.GA3154@tiiu.internal> <3DDEBCDB.4A363410@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DDEBCDB.4A363410@mindspring.com> 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 22, 2002 at 03:25:15PM -0800, Terry Lambert wrote: > > I have now definitive answer for _my_ case and environment. Just > > finished full package build for my workstation bundle port (92 > > ports), including XFree-4, KDE3, mozilla-devel and whatnot. It all > > went very well running kernel which had: > > > > DISABLE_PSE enabled > > DISABLE_PG_G disabled > > > > Are you interested of the reverse? Can it be that enabling > > DISABLE_PSE incorporates DISABLE_PG_G somehow? > > I give up. > > You guys obviously still think it's a software problem that you > can characterize and fix using binary elimination to find the > offending code. It's not. You got me wrong. I'm user and do not know and don't want to know about any CPU architecture and bugs. But I've got problems and simply trying to provide any data possible to gather by myself. Either CPU hardware or software bug, fine. You're claiming to know the bug and possible fix, but don't want to publish it, fine. I don't want to think about it because with my knowledge this is going to nowhere and only wasting my time. Things you see above are my results using consistent testing environment, take it or leave it. I'll stick with DISABLE_PSE enabled and DISABLE_PG_G disabled for the time being. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message