Date: Sat, 02 Mar 2002 15:00:48 -0700 (MST) From: "M. Warner Losh" <imp@village.org> To: doconnor@gsoft.com.au Cc: jerfa@yahoo.com, freebsd-stable@FreeBSD.ORG Subject: Re: Pentium and NO_F00F_HACK = kernel panic Message-ID: <20020302.150048.126438779.imp@village.org> In-Reply-To: <1014889885.13562.16.camel@chowder.gsoft.com.au> References: <200202280123.RAA79623@star-one.liberator.dyndns.org> <20020228092726.2B33037B402@hub.freebsd.org> <1014889885.13562.16.camel@chowder.gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <1014889885.13562.16.camel@chowder.gsoft.com.au>
"Daniel O'Connor" <doconnor@gsoft.com.au> writes:
: On Thu, 2002-02-28 at 20:57, Johann Frisch wrote:
: > > "F00F hack" works around the CPU bug; the NO_F00F_HACK option
: > > disables the workaround.)
: >
: > I knew that and I have no problem using this option. I am just curious
: > if this kernel behaviour is intented or not?
:
: No, it shouldn't panic.
: You should have it on as it wouldn't save you very much space..
: Could you get a stack trace (enable crash dumps etc..) and file a PR
: about it? :)
We boot things on a pentium 133 and 266 with NO_F00F_HACK and have as
recently as 4.5-RELEASE minus a few days.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020302.150048.126438779.imp>