Coreboot PCIe issues on V1210

[danieldk]

Following up on #41. After I flashed Coreboot, I got a lot of PCIe errors on Linux and FreeBSD (opnsense). The issues sometimes resulted in FreeBSD not being able to bring up NVMe. I flashed back the AMI BIOS, but I thought it was useful to report this issue. Example output from FreeBSD:

Root mount waiting for: usbus0
uhub2: 4 ports with 4 removable, self powered
nvme0: Resetting controller due to a timeout.
nvme0: resetting controller
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Resetting controller due to a timeout.
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
nvme0: Waiting for reset to complete
panic: NVME polled command failed to complete within 10s.
cpuid = 0
time = 48
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0064396bc0
vpanic() at vpanic+0x131/frame 0xfffffe0064396cf0
panic() at panic+0x43/frame 0xfffffe0064396d50
nvme_ctrlr_hmb_enable() at nvme_ctrlr_hmb_enable+0x11f/frame 0xfffffe0064396da0
nvme_ctrlr_start() at nvme_ctrlr_start+0x549/frame 0xfffffe0064396e20
nvme_ctrlr_reset_task() at nvme_ctrlr_reset_task+0x96/frame 0xfffffe0064396e40
taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe0064396ec0
taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe0064396ef0
fork_exit() at fork_exit+0x7f/frame 0xfffffe0064396f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0064396f30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 0 tid 100067 ]
Stopped at      kdb_enter+0x33: movq    $0,0xfdcee2(%rip)

[SergeyKonst3]

Thank you for providing this information.

If you have a chance could you please provide some more information. What version of freeBSD/opnsense are you using? Is opnsense installed on the eMMC or the the NVMe drive? Are there any other components present? Just to verify, these errors are not present when using AMI?

We are investigating the possible cause(s) for this issue.

[danieldk]

If you have a chance could you please provide some more information. What version of freeBSD/opnsense are you using?

24.7.7

Is opnsense installed on the eMMC or the the NVMe drive? Are there any other components present? Just to verify, these errors are not present when using AMI?

It's on the NVMe drive. The errors are not present when using AMI.

[SergeyKonst3]

Thank you for providing additional information.

We are looking into this issues.