From owner-freebsd-stable Wed Sep 20 13:29:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from c3-dbn-20.dial-up.net (c3-dbn-20.dial-up.net [196.33.200.20]) by hub.freebsd.org (Postfix) with ESMTP id 01F4937B422; Wed, 20 Sep 2000 13:29:22 -0700 (PDT) Received: (from rnordier@localhost) by c3-dbn-20.dial-up.net (8.8.7/8.6.12) id WAA16295; Wed, 20 Sep 2000 22:27:55 +0200 (SAST) From: Robert Nordier Message-Id: <200009202027.WAA16295@c3-dbn-20.dial-up.net> Subject: Re: BTX error on boot. In-Reply-To: "from John Baldwin at Sep 20, 2000 10:39:18 am" To: John Baldwin Date: Wed, 20 Sep 2000 22:27:52 +0200 (SAST) Cc: Koen Schreel , Freebsd-stable@FreeBSD.ORG, rnordier@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 20-Sep-00 Koen Schreel wrote: > > Hi, > > > > I have a new (dual cpu) system here on which I want to install FreeBSD > > 4.1 but when booting from CDROM or floppy I get the message: > > > > - > > int=0000000d err=00000013 efl=00010046 eip=000093f2 > > eax=00000000 ebx=00000204 ecx=0000000b edx=00001b80 > > esi=00000000 edi=00000005 ebp=000003fc esp=000017dc > > cs=0008 ds=0000 es=0000 fs=0000 gs=0000 ss=0010 > > cs:eip=6a 08 eb 3c 6a 09 eb 38-6a 0a eb 34 6a 0b eb 30 > > ss:esp=91 e8 00 00 00 f0 00 00-46 02 03 00 02 04 00 00 > > BTX halted > > > > System configuration: > > > > MSI 694D Pro motherboard with 2 PIII-800, bios version 1.4 > > 512 MB Memory PC-100 CAS 2 > > Adaptec 29160 U160-SCSI controller with 5 disks > > Matrox G400-DH > > Hmm, it is dying trying to handle a clock interrupt on IRQ0: > > # > # Hardware interrupt jump table. > # > intx20: push $0x8 # Int 0x20: IRQ0 > jmp int_hw # V86 int 0x8 > push $0x9 # Int 0x21: IRQ1 > jmp int_hw # V86 int 0x9 > > It appears to be dying on that push, which makes no sense. However > the err code is 0x13, which is not a valid selector in BTX (well, > selector 0x10 should be at a DPL of 0, not 3), so it _may_ be this > item in the list of GPF exceptions: > > 14.Interrupt or exception via trap or interrupt gate from V86 mode to > privilege level other than zero. > > 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. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message