Date: Mon, 13 Mar 2000 10:56:15 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: Brad Knowles <blk@skynet.be> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.org> Subject: Re: Weirdest crash I ever saw... Message-ID: <200003131532.KAA26127@members.freedomnet.com> In-Reply-To: <v04220807b4f27324ada6@[195.238.1.121]>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13-Mar-00 Brad Knowles wrote: > At 7:38 PM +0100 2000/3/10, Brad Knowles wrote: > >> At 7:23 PM +0100 2000/3/10, Brad Knowles wrote: >> >>> As soon as I can, I'll gdb the crash dump, and post the trace >>>back here. >> >> Okay, here's the traceback with debugging symbols: > > Man, yet another crash on this machine. I've got the serial > console attached, I've got DDB compiled into the kernel, I've got > DEBUGGER_ON_BREAK defined, but none of that helps when the bootloader > is what craps out on me. Here's what I got this time: > > F1 DOS > F2 FreeBSD > F5 Drive 1 > > Default: F2 > > /boot.config: -P > Keyboard: no > > int=00000000 err=00000000 efl=00030083 eip=00000004 > eax=000004e3 ebx=0000097f ecx=0000dc00 edx=000034be > esi=0000dc00 edi=00000004 ebp=00000000 esp=000004ce > cs=c800 ds=c800 es=9e7d fs=0000 gs=0000 ss=9e7b > cs:eip=d4 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > System halted > > I hope I typed that in correctly. Ok, that is useful. Sort of. Are you sure that int number is right? int=0 is a Divide by Zero error, where as the instruction you died on is an 'out' instruction, which does I/O, not math. This is some sort of expansion ROM BIOS for some card you have. What hardware is in this system? > Anyway, I'm pretty sure that I'm using the latest boot blocks and > bootloader -- I followed steps #4 & #5 of 14.5.4.2 of the Handbook > (see <http://www.freebsd.org/handbook/x10359.html>) after my most > recent installworld (from late last week), and I had to do a "make > clean; make install" in each case. > > I just pressed the reset switch and rebooted, and this occurred > again with exactly the same values, etc... -- it appears that this > problem is reproducible. I'm going to try rebooting with the > keyboard plugged in, so that I can see if this makes a difference. > > Is any of this of actually any help to anyone on this list, or > should I be posting these questions/updates to some other list (e.g., > -current, or -hackers)? A BTX fault like the above is useful to myself at least, and potentially anyone else who does x86 assembly foo. -- John Baldwin <jhb@FreeBSD.org> -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003131532.KAA26127>