[Bug 268384] HGST NVME U.2 Disk not accessible for releases prior to 13.1-STABLE

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

            Bug ID: 268384
           Summary: HGST NVME U.2 Disk not accessible for releases prior
                    to 13.1-STABLE
           Product: Base System
           Version: 13.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: nb@synthcom.com

Created attachment 238803
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238803&action=edit
13.1-RELEASE Dmesg.boot file (this is from working nvme0)

I have an Asus server motherboard that will not install FreeBSD directly to
NVME 2.5" U.2 disks. The symptom is that it doesn't show nvme0 as an option for
a destination install. FreeBSD 12.x, 13.0, and 13.1-RELEASE all have the issue.
13.1-STABLE And 14 both *DO* properly recognize the NVME controller. It does
install just fine to any M.2 NVME disks in the system and sees those just fine
regardless of version.

For the FreeBSD installs that fail, dmesg.boot for nvme0 shows as follows:

nvme0: <WDC SN200> at device 0.0 numa-domain 0 on pci4
nvme0: unable to allocate pci resource
nvme0: <WDC SN200> at device 0.0 numa-domain 0 on pci4
nvme0: unable to allocate pci resource

System details:

* Asus RS700A-E11-RS12U, dual AMD Epyc 7742 CPUs
* BIOS version is 0702. Latest is 1205. Have not been able to successfully
update.
* 512GB of memory
* HGST Ultrastar HUSMR7676BDP3Y1 SN200 U.2 NVME disk (this only works with
13.1-STABLE And newer)
* Dual EVO 980 M.2 NVME disks (these ALWAYS work)

I've attached a dmesg boot from the 13.1-STABLE release in case its helpful at
all. Is this something that has a workaround or is just lack of support?

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