From owner-freebsd-questions Tue Mar 23 22:10:44 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 1CC6A153B2 for ; Tue, 23 Mar 1999 22:10:41 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id AAA23104; Wed, 24 Mar 1999 00:10:20 -0600 (CST) Date: Wed, 24 Mar 1999 00:10:19 -0600 From: Dan Nelson To: Gavan Anderson Cc: "freebsd-questions@FreeBSD.ORG" Subject: Re: P133 Question Message-ID: <19990324001019.A22965@dan.emsphone.com> References: <199903240018.AAA38912@out2.ibm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903240018.AAA38912@out2.ibm.net>; from "Gavan Anderson" on Wed Mar 24 11:18:32 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 24), Gavan Anderson said: > I just set up a 2.2.8 installation on a Pentium 133. On boot up as it > scans through the hardware, one of the messages returned states: > > "Pentium F00F detected .. installing workaround" > > What does this really mean? Do I have a problem with that version of > the Pentium processor, or is it something broken in the INTEL > instruction set? It basically means you have a Pentium. All Pentiums are susceptible to the "F00F" bug, where a certain machine-language instruction (starting with the hex digits F0 0F) can lock the CPU up tight, requiring a physical reset. The workaround alters the system so that the instruction is trapped before any damage is done. In 2.2-STABLE and later (i.e. 3.* and 4.*), the wording has been changed to: "Intel Pentium detected, installing workaround for F00F bug" which, if nothing else, is at least grammatically correct :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message