Date: Wed, 11 Feb 2026 17:15:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 293117] FreeBSD crashes on boot when NVMe disk with non-zero metadata size is installed Message-ID: <bug-293117-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293117 Bug ID: 293117 Summary: FreeBSD crashes on boot when NVMe disk with non-zero metadata size is installed Product: Base System Version: 16.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bcran@FreeBSD.org When using the 16.0-CURRENT 20260209 aarch64 snapshot, I get a kernel panic if there's an NVMe drive installed that's been formatted with a non-zero metadata size. The system is an ASRock Rack AMPONED8-2T/BCM with AmpereOne A192-32X and 64GB RAM. With zero metadata: # NVMe list: Node Generic SN Model Namespace Usage Format FW Rev --------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- -------- /dev/nvme0n1 /dev/ng0n1 48941289800258 Sabrent SB-P4U2-1920 0x1 1.92 TB / 1.92 TB 4 KiB + 0 B EKFP34AE /dev/nvme1n1 /dev/ng1n1 48941289800234 Sabrent SB-P4U2-1920 0x1 1.92 TB / 1.92 TB 4 KiB + 8 B EKFP34AE /dev/nvme2n1 /dev/ng2n1 25243Z802301 WD_BLACK SN8100 2000GB 0x1 2.00 TB / 2.00 TB 4 KiB + 0 B 830ZRR02 # Namespace identify: LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 3 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 4 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best # After running "nvme format --lba=3 /dev/nvme1n1": Node Generic SN Model Namespace Usage Format FW Rev --------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- -------- /dev/nvme0n1 /dev/ng0n1 48941289800258 Sabrent SB-P4U2-1920 0x1 1.92 TB / 1.92 TB 4 KiB + 0 B EKFP34AE /dev/nvme1n1 /dev/ng1n1 48941289800234 Sabrent SB-P4U2-1920 0x1 1.92 TB / 1.92 TB 4 KiB + 8 B EKFP34AE /dev/nvme2n1 /dev/ng2n1 25243Z802301 WD_BLACK SN8100 2000GB 0x1 2.00 TB / 2.00 TB 4 KiB + 0 B 830ZRR02 Panic booting FreeBSD 16.0-CURRENT main-n283862-89aa8a94053f GENERIC arm64: nda0: <Sabrent SB-P4U2-1920 EKFP34AE 48941289800258> nda0: Serial Number 48941289800258 nda0: nvme version 1.4 nda0: 1831420MB (468843606 4096 byte sectors) nda1 at nvme1 bus 0 scbus1 target 0 lun 1 nda1: <Sabrent SB-P4U2-1920 EKFP34AE 48941289800234> nda1: Serial Number 48941289800234 nda1: nvme version 1.4 nda1: 1831420MB (468843606 4096 byte sectors) nda2 at nvme2 bus 0 scbus2 target 0 lun 1 nda2: <WD_BLACK SN8100 2000GB 830ZRR02 25243Z802301> nda2: Serial Number 25243Z802301 nda2: nvme version 2.0 nda2: 1907729MB (488378646 4096 byte sectors) APEI Fatal Error 2826cc9f-448c-4c2b-86b6-a95394b7ef33: Error Data: 02 00 02 00 71 01 00 00 00 00 00 00 00 00 00 00 0f 01 00 00 00 00 00 00 00 00 00 ec 00 00 00 00 00 00 00 00 00 00 00 80 cc 39 00 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Flags: 0x0 panic: APEI Fatal Hardware Error! cpuid = 0 time = 2 KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x38 vpanic() at vpanic+0x1a0 panic() at panic+0x48 apei_ge_handler() at apei_ge_handler+0xa54 apei_notify_handler() at apei_notify_handler+0x28 AcpiEvNotifyDispatch() at AcpiEvNotifyDispatch+0x44 acpi_task_execute() at acpi_task_execute+0x18 taskqueue_run_locked() at taskqueue_run_locked+0x17c taskqueue_thread_loop() at taskqueue_thread_loop+0xc0 fork_exit() at fork_exit+0x78 fork_trampoline() at fork_trampoline+0x18 KDB: enter: panic [ thread pid 0 tid 102611 ] Stopped at kdb_enter+0x48: str xzr, [x19, #768] -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293117-227>