[Bug 272507] SATA controller fails to initialize on some AMD X670E(xtreme) based motherboards

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272507

--- Comment #9 from Justin Tocci <justin@tocci.org> ---
Items with arrows were messed with. (original setting) -> (what i tried)

BIOS settings:
 Boot menu:
  CSM enabled -> disabled
  Launch PXE OpROM Policy UEFI -> Do not launch
  Launch Storage OpROM Policy UEFI -> Do not launch
  Full Screen Logo Enabled -> disabled
  fast boot disabled

 Security Menu:
  Supervisor Password Not installed
  user password Not Installed
  HDD Security Configuration:
   P0:ST8000NE0004-1ZF11G   <- SATA drive that won't show in FreeBSD
   P1:ST12000NM000J-2TY103  <- SATA drive that won't show in FreeBSD

 Advanced\Storage Configuration Menu:
  SATA Mode AHCI
  SATA Port 1 Hot Plug Enabled -> disabled
  SATA Port 2 Hot Plug Enabled -> disabled
  SATA Port 3 Hot Plug Enabled -> disabled
  SATA Port 4 Hot Plug Enabled -> disabled
  SATA port1 ST8000NE0004-1 (8001.5GB)
  SATA Port2 ST12000NM000J- (12000.1GB)

 OC Tweaker Menu: (I had not touched this menu previously)
  (there are two pages of stuff here, all marked 'Auto'. i left it alone.)

 Advanced\Trusted Computing Menu:(I had not touched this menu previously)
  Security Device Support (TPM2.0): Enable
  SHA256 PCR Bank Enabled
  SHA384 PCR Bank Disabled
  Pending Operation None
  Platform Hierarchy Enabled
  Storage Hierarchy Enabled -> Disabled
  Endorsement Hierarchy Endabled
  Physical Presence Spec Version 1.3
  Device select auto

I also tried:
 RGB LED On/Off on -> off
 Above 4G Decoding enabled -> disabled
 Re-Size Bar support enabled -> disabled

So the above was about a dozen reboots. Last thing I did was reset all settings
to default.

Each time I rebooted i checked for drives in /dev. no 'da' devices showed but i
also looked for anything unusual.

I also did an 'ls /dev/diskid' to see if anything showed there.

Then I did a gpart show and gpart list. No joy there either.

Note that the bios has no problem listing the drives on two screens so it seems
there is something going right at that point. 

first issue in dmesg still seems to be:
Firmware Error (ACPI): Failure creating named object [\134_SB.PCI0.GPP0._PRW],
AE_ALREADY_EXISTS (20201113/dswload2-480)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20201113/psobject-372)
Firmware Error (ACPI): Failure creating named object [\134_SB.PCI0.GPP2._PRW],
AE_ALREADY_EXISTS (20201113/dswload2-480)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20201113/psobject-372)
Firmware Error (ACPI): Failure creating named object [\134_GPE._L08],
AE_ALREADY_EXISTS (20201113/dswload2-480)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20201113/psobject-372)

Also, SATA issues remain:
root(33)au:~ # cat /var/log/dmesg.today | grep -A 2 SATA
ahci0: <AHCI SATA controller> at device 0.0 on pci18
ahci0: 0x400 bytes of rid 0x24 res 3 failed (0, 0xffffffffffffffff).
device_attach: ahci0 attach returned 6
--
ahci0: <AHCI SATA controller> mem 0xfc580000-0xfc5803ff at device 0.0 on pci20
ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
--
ahci1: <AHCI SATA controller> at device 0.0 on pci18
ahci1: 0x400 bytes of rid 0x24 res 3 failed (0, 0xffffffffffffffff).
device_attach: ahci1 attach returned 6
--
ahci1: <AHCI SATA controller> at device 0.0 on pci18
ahci1: 0x400 bytes of rid 0x24 res 3 failed (0, 0xffffffffffffffff).
device_attach: ahci1 attach returned 6


Please don't hesitate to let me know if there is something else I can do.

-- 
You are receiving this mail because:
You are the assignee for the bug.