[Bug 271276] Needs reboot to detect NVMe disk after hot add NVMe controller and disk separately in FreeBSD 12.x and 13.x

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 06 May 2023 15:42:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271276

--- Comment #1 from Yuri Pankov <yuripv@FreeBSD.org> ---
Could you test with with nda(4) and/or -CURRENT, as this combination seems to
work for me, running main-n262599-60167184abd5:

(adding controller, pressing OK)
nvme1: <VMware NVMe Controller> at device 2.0 on pci2
nvme1: temperature threshold not supported

(adding "disk" to first controller that existed at boot, pressing OK)
nvme0: async event occurred (type 0x2, info 0x00, page 0x04)
nda1 at nvme0 bus 0 scbus2 target 0 lun 2
nda1: <VMware Virtual NVMe Disk 1.3 VMware NVME_0000>
nda1: Serial Number VMware NVME_0000
nda1: nvme version 1.3 x32 (max x32) lanes PCIe Gen2 (max Gen2) link
nda1: 8192MB (16777216 512 byte sectors)

(adding "disk" to newly added controller, pressing OK)
nvme1: async event occurred (type 0x2, info 0x00, page 0x04)
nda2 at nvme1 bus 0 scbus3 target 0 lun 1
nda2: <VMware Virtual NVMe Disk 1.3 VMware NVME_0001>
nda2: Serial Number VMware NVME_0001
nda2: nvme version 1.3 x32 (max x32) lanes PCIe Gen2 (max Gen2) link
nda2: 8192MB (16777216 512 byte sectors)

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