From owner-freebsd-current Tue Aug 3 12:21:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 978A4152D3 for ; Tue, 3 Aug 1999 12:21:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA03722; Tue, 3 Aug 1999 09:57:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908031657.JAA03722@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jonathan Lemon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Tue, 03 Aug 1999 10:58:45 CDT." <19990803105845.19595@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Aug 1999 09:57:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 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. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message