Bug 130110 - [boot] BTX-Halted - booting with SAS/SATA Controller
Summary: [boot] BTX-Halted - booting with SAS/SATA Controller
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: i386 (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-i386 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 09:10 UTC by srinivas
Modified: 2019-01-07 18:06 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description srinivas 2009-01-02 09:10:03 UTC

Installing the Free BSD with SAS/SATA Controller upon rebooting gives
BTX-Halted problem. I have installed the Free BSD successfully without
SAS/SATA Controller. 

My Investigation on this.

It reached boot0 stage (i.e) it was able to read MBR and able to find
the bookable image in the drive.

And it displayed
	
      Default: F1

If I press enter, it tried to execute boot2 stage and it prints the error
BTX HALTEDwith some register information.

After pressing enter, it sent the following commands to BIOS service.

0x02  read  --- successful
0x03 -- write -- successful
0x02  read -- successful
0x41  extension check-- successful
0x42  extended read-- successful
0x41  extension check-- successful
0x42  extended read-- successful
0x41  extension check-- successful
0x42  extended read  -------------- when BIOS tried to execute this command, it prints error BTX halted 

Here,  We have OS loader code( Boot0 & boot2) at one side, which will
send BIOS service commands( as listed above) to BIOS services and BIOS
service tried to execute it, giving the response to OS loader code.
While executing the Boot2 code, it prints the error BTX halted. 

In this scenario, we did check the following things,
1.	stack corruption  --  no stack corruption
2.	command failed or not.  all the command was successful till that
	point.
3.	commands sent out by the OS loader code --- usual commands like
	0x02,0x41,0x42,....( except 0x03)

Fix: 

I have no idea.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-01-02 09:58:15 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-i386

reclassify.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:18 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Warner Losh freebsd_committer freebsd_triage 2019-01-07 18:06:08 UTC
Since there's no model / card name/number, we can't reproduce this to see if it's an issue. In addition, a number of fixes have been made to the BIOS routines since this bug was filed, and they cope better with errors.