From owner-freebsd-current Sun May 30 13: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id EFC6C14DBE for ; Sun, 30 May 1999 13:04:35 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA00369; Sun, 30 May 1999 13:54:14 -0600 (MDT) Date: Sun, 30 May 1999 13:54:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905301954.NAA00369@narnia.plutotech.com> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) X-Newsgroups: pluto.freebsd.current In-Reply-To: <199905291437.AAA04536@godzilla.zeta.org.au> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, it works on a Celeron but fails on a P5. This is caused by the > following bug suite (in approximately historical order): > 1) IRQ13 interface was broken as designed. > 2) Intel F00F bug. > 3) Probe for (1) is not very well implemented. It hacks on the idt[] > global to context switch some IDT entries. > 4) Fix for (2) is not very well implemented. It moves the IDT without > hiding idt[] from (3). > 5) Rev.1.55 of disturbed the probe order so that (4) is > done before (3). This breaks the IDT context switching if the F00F > fix gets installed. npx traps and interrupts end up being serviced > by the dummy probe routines. Do you record this stuff anywhere? I think we should have a Bruce's nits page so this stuff isn't forgotten. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message