On Fri, Oct 27, 2000 at 12:46:05AM -0700, Matt Dillon wrote:
> This is really weird. I have two valinux rackmount boxes, duel cpu's.
>
> 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).
>
> I messed around trying to track down where the loader was dying. I
> found it was dying in v86int(), called from bd_int13probe() in
> libi386/biosdisk.c. It seems to be dying in the BIOS itself.
It looks pretty similar to famous BIOS virus protection thingy. Can
this be the case?
Cheers,
%Anton.
--
<img align="lawful"> and <img align="chaotic"> would be a nice addition
to HTML specification.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
