From owner-freebsd-hackers Sat Jul 1 11:54: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id 0F49537B69A; Sat, 1 Jul 2000 11:54:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA00878; Sat, 1 Jul 2000 20:53:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: KATO Takenori Cc: msmith@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sun, 02 Jul 2000 02:44:54 +0900." <20000702024454G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 01 Jul 2000 20:53:56 +0200 Message-ID: <876.962477636@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000702024454G.kato@gneiss.eps.nagoya-u.ac.jp>, KATO Takenori writ es: >Poul-Henning Kamp wrote: > >> Look at the first paragraph: This is for Pentium Pro cpus running >> in motherboards where the BIOS does not contain the needed microcode >> updates. > >I have one question. Does microcode update modify a CPU permanently? No, it needs to be loaded at every reboot. >I used a CPU on the M/B with correct microcode update and then moved >the CPU to the M/B which has signal 11 problem. Signal 11 didn't >disappear. This must have other reasons. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message