From owner-freebsd-hackers  Fri Oct 27  2:12:24 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7435337B661; Fri, 27 Oct 2000 02:12:18 -0700 (PDT)
Received: (from daemon@localhost)
	by smtp04.primenet.com (8.9.3/8.9.3) id CAA01298;
	Fri, 27 Oct 2000 02:09:08 -0700 (MST)
Received: from usr09.primenet.com(206.165.6.209)
 via SMTP by smtp04.primenet.com, id smtpdAAAZXaaDc; Fri Oct 27 02:09:04 2000
Received: (from tlambert@localhost)
	by usr09.primenet.com (8.8.5/8.8.5) id CAA26546;
	Fri, 27 Oct 2000 02:12:10 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <200010270912.CAA26546@usr09.primenet.com>
Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux hardware
To: dillon@earth.backplane.com (Matt Dillon)
Date: Fri, 27 Oct 2000 09:12:10 +0000 (GMT)
Cc: freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG),
	hackers@FreeBSD.ORG
In-Reply-To: <200010270746.e9R7k5k00392@earth.backplane.com> from "Matt Dillon" at Oct 27, 2000 12:46:05 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>     I was testing the PXE stuff and booting one of the boxes regularly.  
>     All of a sudden every time I reboot I get:
> 
> ...
> BIOS drive A: is disk0
> 
> int=00000000 err=00000000 efl=00030246 eip=00001d29
> eax=00000000 ebs=00000390 ecx=00000000 edx=00000000
> esi=00008db7 edi=00001c09 ebp=00000398 esp=0000038c
> cs=c800 ds=0040 es=8db7 fs=0000 gs=0000 ss=8db7
> cs:eip= f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff
> ss:esp= 00 00 3f 00 00 00 00 00-00 00 02 00 22 0a 00 c8
> BTX halted
> 
>     *All* the time.  That is, everything was working fine, then nothing was
>     working.  Powering down doesn't help... now every boot comes up with the
>     above error.  I didn't change the boot image ... in fact, when I stuck
>     the 4.1 CD in the now non-working machine, *IT's* bootloader also 
>     crashed every time too (and it worked previously).

Too bad you killed your test case, or it might have gotton fixed;
you made an image backup before you blew away the labels, or not?

I think you might want to consider putting a DELAY after the BIOS
call itself; perhaps some device that was poked by the BIOS is
latching the bus, and you are doing an INB or OUTB too soon after
the fact (but that's just my gut reaction to a crash following a
BIOS call...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message