Bug 143587 - [boot] [hang] BTX 1.02 freezes upon assigning Bios C drive from Serveraid based array [regression]
Summary: [boot] [hang] BTX 1.02 freezes upon assigning Bios C drive from Serveraid bas...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: i386 (show other bugs)
Version: 6.4-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-i386 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-05 20:30 UTC by Ricky Dee
Modified: 2019-01-08 19:02 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ricky Dee 2010-02-05 20:30:03 UTC 
FreeBSD 5.5 and before do not exhibit the problem since they use BTX
1.01.  If I try to boot the system on FreeBSD 6.4 which uses BTX 1.02
and an array is defined in the serveraid adapter (tried Serveraid 3L,
4L, 4Lx, etc.) the boot freezes when trying to assign bios drive C right
after Bios A drive is assigned.  It does not halt or provide any
information, it just freezes.  If the serveraid adapter has no array
defined, drive c is not assigned and booting works but installation
fails since no drive is present to install.  Same behaviour whether cd
or disks are used to boot.  I tried on on IBM x326m, IBM x300 and IBM
x306m with same results.

How-To-Repeat: Configure a raid-1 array on a scsi based serveraid adapter 3L, 4L, 4Lx
and try to boot FreeBSD with a BTX 1.02 (6.4-Release or more) and the
freeze should occur.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:11 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 2 Warner Losh freebsd_committer freebsd_triage 2019-01-08 19:02:14 UTC 
We've done a lot with BTX since 6.4R, so I'm going to close this bug as fixed. If there's still an issue with FreeBSD 11 or 12, please file a new bug and cc me so we can work through this issue.