From owner-freebsd-stable Thu Sep 21 9:54:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 757F137B43E for ; Thu, 21 Sep 2000 09:54:24 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA01154; Wed, 20 Sep 2000 22:23:26 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009210523.WAA01154@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Nordier Cc: Freebsd-stable@freebsd.org Subject: Re: BTX error on boot. In-reply-to: Your message of "Wed, 20 Sep 2000 22:27:52 +0200." <200009202027.WAA16295@c3-dbn-20.dial-up.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 22:23:26 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However, for that to be the case, BTX's IDT would have to be fubar'd. > > Looking at the stack, it looks like it was at 0xf000:91e8 in the previous > > frame, which would be in the BIOS and thus in VM86 mode. Robert, do you > > have any ideas? > > I haven't really had a chance to look at this, but maybe we're looking > at an interrupt #19 (SIMD exception), since this is a PIII. Anyway, I > haven't seen BTX do this before, and the bottom line is probably just > that it isn't going to work unless the hardware configuration changes. ie. you feel that the system BIOS is simply incompatible with BTX, or that there's no way that BTX could ever deal with this situation? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message