From owner-freebsd-current Thu Apr 18 7:23:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 69F2537B405 for ; Thu, 18 Apr 2002 07:23:24 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA11840; Fri, 19 Apr 2002 00:23:14 +1000 Date: Fri, 19 Apr 2002 00:23:50 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: What does "FPU bounds check fault" mean? In-Reply-To: <3CBDF3DC.6347FC29@vicor-nb.com> Message-ID: <20020419002106.U15456-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Apr 2002, Julian Elischer wrote: > I got this fault on a production machine.. > The given fault PC was 0xc01499f0 which is the first byte of fxpintr() > (??) > even though coredumps were enabled, for some reason none was made. > > > > > > > > > wss0c left this message in /var/log/messages: > > > > Apr 17 08:36:55 wss0c /kernel: Fatal trap 21: "FPU bounds check fault > > > > while in kernel mode "FPU" means that i386/trap.c has a bogus error message for the non-FPU bounds check fault. I think the kernel doesn't use the `bounds' instruction, so the bug is most likely that a garbage instruction was executed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message