Date: Fri, 22 Nov 2002 18:24:43 +0200 From: Vallo Kallaste <kalts@estpak.ee> To: John Baldwin <jhb@FreeBSD.org> Cc: Terry Lambert <tlambert2@mindspring.com>, current@FreeBSD.org, Scott Sipe <cscotts@mindspring.com> Subject: Re: DP2 Fatal Trap Message-ID: <20021122162443.GA3154@tiiu.internal> In-Reply-To: <XFMail.20021122105742.jhb@FreeBSD.org> References: <3DDD7C44.84C0D242@mindspring.com> <XFMail.20021122105742.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 22, 2002 at 10:57:42AM -0500, John Baldwin <jhb@FreeBSD.org> wrote: > > It has an effect: writing CR3 or a TSS resulting in a changed CR3 > > will not invalidate TLB entries with the G flag set, if PGE is set > > in CR4. > > I know what PG_G does, Terry. My question is that if DISABLE_PG_G has > no effect on the _problems_ people are having. 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? -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021122162443.GA3154>