Bug 169455 - [boot] BTX loader panics on Opteron3280
Summary: [boot] BTX loader panics on Opteron3280
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: i386 (show other bugs)
Version: 9.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-i386 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-26 19:10 UTC by NAKAMURA Kazushi
Modified: 2019-01-07 18:40 UTC (History)
2 users (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 NAKAMURA Kazushi 2012-06-26 19:10:08 UTC 
        BTX loader panics on Opteron3280.
	The default CPU, AMD Sempron on Fujitsu Primergy MX130S2 Server Machine
	can boot up FreeBSD, it's no problem.
	But replace Sempron to Opteron3280, BTX loader panics not only HDD
	but also CD-ROM. I tried FreeBSD7.4, 8.3, 9.0 x amd64, i386,
	but all of them panic.

	NetBSD5.1 and OpenBSD5.1 is OK. They are boot up, no problem.

Fix: 

Sorry, yet.
-- 
NAKAMURA Kazushi@KOBE	@http://kobe1995.jp/~kaz/@
BSD Associate certificated
- Break the hate chain. No more kill!
administrator@[127.1]
How-To-Repeat:         Power on the server machine, boot from HDD or CD-ROM.
	There is dmesg of Sempron Primergy MX130S2.
	http://kobe1995.jp/~kaz/dmesg/Fujitsu/MX130S2/
	NetBSD and OpenBSD on Opteron3280's dmesg is
	http://kobe1995.jp/~kaz/dmesg/Fujitsu/MX130S2_Opteron3280/
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-06-26 20:45:12 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-i386

Also happens on amd64, but just pick one for GNATS.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:15 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:40:26 UTC 
We've done a lot of fixes to BTX since this bug was filed dealing with panics. I'm not able to determine what to try to reproduce. Please file a new bug report and CC me if this is still a problem.