Re: What does "FPU bounds check fault" mean?

[Bruce Evans]

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

What does "FPU bounds check fault" mean?

[Julian Elischer]

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
> > > Apr 17 08:36:55 wss0c /kernel: instruction pointer  = 0x8:0xc01499f0
> > > Apr 17 08:36:55 wss0c /kernel: stack pointer=
> > > 0x10:0xd9f83f9c
> > > Apr 17 08:36:55 wss0c /kernel: frame pointer=
> > > 0x10:0xbfbffc8c
> > > Apr 17 08:36:55 wss0c /kernel: code segment = base 0x0, limit
> > > 0xf, type 0x1b
> > > Apr 17 08:36:55 wss0c /kernel: = DPL 0, pres 1, def32 1, gran 1
> > > Apr 17 08:36:55 wss0c /kernel: processor eflags = interrupt enabled,
> > > IOPL = 0
> > > Apr 17 08:36:55 wss0c /kernel: current process  = 78317 (gzip)
> > > Apr 17 08:36:55 wss0c /kernel: interrupt mask   = net
> > > Apr 17 08:36:55 wss0c /kernel: trap number  = 21
> > > Apr 17 08:36:55 wss0c /kernel: panic: FPU bounds check fault
> > > Apr 17 08:36:55 wss0c /kernel:
> > >

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message