Bug 199605

Summary: BTX halted
Product: Base System Reporter: Karli Sjöberg <Karli.Sjoberg>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed Not Enough Information    
Severity: Affects Only Me CC: Karli.Sjoberg, imp
Priority: ---    
Version: 10.1-STABLE   
Hardware: amd64   
OS: Any   

Description Karli Sjöberg 2015-04-22 09:27:36 UTC
I was just upgrading one of our storage's- an old Sun Fire X4140- to 10.1-STABLE as per Bug 191348[*] when something strange happened after writing new boot code and rebooting:

BTX loader 1.00  BTX version is 1.02
Consoles: internal video/keyboard
BIOS drive C: is disk8
BIOS drive D: is disk9

int=00000000  err=00000000  efl=00010246  eip=00037d34
eax=00000001  ebx=00000000  ecx=00000000  edx=00000000
esi=00000000  edi=00000000  ebp=0008f600  esp=0008f598
cs=002b  ds=0033  es=0033    fs=0033  gs=0033  ss=0033
cs:eip=f7 35 d0 f4 03 00 85 f6-74 05 89 3e 89 5e 04 89
       c2 e9 cc 00 00 00 66 c7-45 ea 00 00 89 d8 c1 e8
ss:esp=00 00 20 00 00 00 00 00-00 00 00 00 00 00 00 00
       00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted

Never happened to me before. I then booted with a 10.1-RELEASE CD and wrote bootcode from that, same problem. 9.3; same there...

Thanks in advance!
Karli Sjöberg

[*]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Comment 1 Karli Sjöberg 2015-04-29 11:42:09 UTC
After doing a binary walk, just doing a default, guided ZFS-on-root install, I can say that:

FreeBSD-9.3-RELEASE  - worked
FreeBSD-10.0-RELEASE - failed
FreeBSD-10.1-RELEASE - failed

Installing 10.1 on UFS works and boots just fine. 10.0 didn´t womit like 10.1, it just gave me the finger:)

--------------------------------------------------------------------------------
|
























--------------------------------------------------------------------------------

That´s all it printed.

/K
Comment 2 Warner Losh freebsd_committer freebsd_triage 2019-01-07 18:58:40 UTC
I think this bug has been fixed. However, there's not enough information to know. Please let me know if you can recreate this on FreeBSD 11 or 12 and file a new bug if so.