Bug 226574

Summary: 12.0 CURRENT & 11.1 Installation on AMD EPYC (BIOS - RSW1005E)
Product: Base System Reporter: Surya <suryakiran3516>
Component: miscAssignee: John Baldwin <jhb>
Status: Closed DUPLICATE    
Severity: Affects Some People CC: emaste, phk, suryakiran3516
Priority: ---    
Version: CURRENT   
Hardware: amd64   
OS: Any   
URL: https://lists.freebsd.org/pipermail/freebsd-current/2018-April/069172.html
Attachments:
Description Flags
Error on console
none
log none

Description Surya 2018-03-13 15:04:24 UTC 
#1
Hi Team,

Tried several times to install FreeBSD 11.1 and 12.0 CURRENT on AMD EPYC processor with BIOS - RSW1005E, installation is getting failed. 

For 11.1, Kernel Crash is happening, system is rebooting and for 12.0 CURRENT, its not crashing but installation getting failed.

Attaching the screenshots for more details.

Kindly help us in installing the FreeBSD 11.1 & 12.0 CURRENT on AMD EPYC Processor.

Steps or process to be followed would be great if someone provide us.

Appreciate your quick help.
Comment 1 Surya 2018-03-16 05:39:36 UTC 
As workaround we tried FreeBSd installation 11.X on the 1p Diesel machine(1P,EPYC 7351-16core) , I am able to install FreeBSD with latest BIOS. I think our issue is with FreeBSD not working with 2P systems. Can someone suggest on this. We will have to dig deeper as to understand why 2P(EPYC 32 core devices (7601)) is not supported. Is it due to FreeBSD OS not having the support for 2P systems or some issue from AMD side.
Comment 2 Surya 2018-03-16 05:41:15 UTC 
Created attachment 191542 [details]
Error on console
Comment 3 Andriy Gapon freebsd_committer freebsd_triage 2018-03-16 08:19:39 UTC 
(In reply to Surya from comment #2)
Can you make a plain text attachment?
Comment 4 Surya 2018-03-19 04:42:17 UTC 
Created attachment 191616 [details]
log
Comment 5 Ed Maste freebsd_committer freebsd_triage 2018-06-13 18:15:52 UTC 
*** Bug 228646 has been marked as a duplicate of this bug. ***
Comment 6 John Baldwin freebsd_committer freebsd_triage 2019-02-13 21:29:06 UTC 

*** This bug has been marked as a duplicate of bug 229429 ***