> > > Fatal trap 9: general protection fault while in kernel mode
> > > instruction pointer = 0x48:0x8034
> > > stack pointer = 0x10:0xc0279e98
> > > frame pointer = 0x10:0x67890000
> > > code segment = base 0xc00f0000, limit 0xffff, type 0x1b
> > > = DPL 0, pres 1, def32 1, gran 0
> > > processor eflags = interrupt enabled, resume, IOPL = 0
> >
> > Why is IOPL zero? I've also noted that making a bios16 call also
> > results in IOPL being zero (I have more that I want to take up with you
> > on that at some stage, since it's got me stumped, but one thing at a
> > time).
>
> The IOPL should be zero, in order to virtualize interrupts. If it's
> more than zero, the BIOS code can turn off interrupts, which isn't
> something we want to do.
Ok. I'm presuming then that we have a tss in place that allows I/O
operations? That was my major concern...
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\ -- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
