Hello,
I would appreciate advice on diagnosing occasional correctable PCIe errors on a Minisforum M1 Pro 285H running Proxmox VE.
Hardware:
- Intel Core Ultra 9 285H; ARBSC motherboard, revision 1.0.
- AMI BIOS 1.01, dated 2025-06-19.
- Kingston OM8TAP41024K1-A00 NVMe, firmware P4ER3B31.
- NVMe endpoint 0000:55:00.0 behind root port 0000:00:1c.0; observed link 16 GT/s x4.
- Active CPU microcode 0x11a.
The issue occurs with both 7.0.14-24-pve and 7.0.14-25-pve. Representative log excerpt:
A log extraction found 35 events from October 16 to 20, 2026 (1, 5, 6, 19 and 4 respectively). These are partial days with reboots, so the counts are not directly comparable rates. The latest event in that extraction occurred on October 20 at 15:57 CEST, after booting -25 that morning.
Checks so far:
- Targeted log searches found no I/O errors, NVMe timeouts, resets or aborts.
- SMART showed 1 Media/Data Integrity Error and 5 Unsafe Shutdowns, unchanged across the checks. Their dates are unknown; no link to the PCIe events has been established. The NVMe error log was empty and short/extended self-tests passed.
- Errors predate GPU passthrough experiments.
- A temporary test disabled only ASPM L1.2, leaving L1 and PCI-PM L1.2 enabled. No new RxErr appeared during approximately three hours, but that is too short to establish a fix. Reboot restored L1.2; no permanent change has been made.
- I could not find BIOS controls for ASPM/L1.2 or PCIe link speed.
I have read the existing "NVME correctable errors?" thread, but have not established whether the same cause applies here.
Has anyone seen this combination of hardware and kernel? Is there a known ASPM/L1-substate or -pve kernel issue worth checking? What controlled tests and diagnostic output would best distinguish power-management behavior from an SSD/slot/link problem?
I want to diagnose the cause rather than hide AER messages. I can provide sanitized pveversion -v, kernel command line and lspci output if useful.
Thank you.
I would appreciate advice on diagnosing occasional correctable PCIe errors on a Minisforum M1 Pro 285H running Proxmox VE.
Hardware:
- Intel Core Ultra 9 285H; ARBSC motherboard, revision 1.0.
- AMI BIOS 1.01, dated 2025-06-19.
- Kingston OM8TAP41024K1-A00 NVMe, firmware P4ER3B31.
- NVMe endpoint 0000:55:00.0 behind root port 0000:00:1c.0; observed link 16 GT/s x4.
- Active CPU microcode 0x11a.
The issue occurs with both 7.0.14-24-pve and 7.0.14-25-pve. Representative log excerpt:
Code:
nvme 0000:55:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
nvme 0000:55:00.0: [ 0] RxErr (First)A log extraction found 35 events from October 16 to 20, 2026 (1, 5, 6, 19 and 4 respectively). These are partial days with reboots, so the counts are not directly comparable rates. The latest event in that extraction occurred on October 20 at 15:57 CEST, after booting -25 that morning.
Checks so far:
- Targeted log searches found no I/O errors, NVMe timeouts, resets or aborts.
- SMART showed 1 Media/Data Integrity Error and 5 Unsafe Shutdowns, unchanged across the checks. Their dates are unknown; no link to the PCIe events has been established. The NVMe error log was empty and short/extended self-tests passed.
- Errors predate GPU passthrough experiments.
- A temporary test disabled only ASPM L1.2, leaving L1 and PCI-PM L1.2 enabled. No new RxErr appeared during approximately three hours, but that is too short to establish a fix. Reboot restored L1.2; no permanent change has been made.
- I could not find BIOS controls for ASPM/L1.2 or PCIe link speed.
I have read the existing "NVME correctable errors?" thread, but have not established whether the same cause applies here.
Has anyone seen this combination of hardware and kernel? Is there a known ASPM/L1-substate or -pve kernel issue worth checking? What controlled tests and diagnostic output would best distinguish power-management behavior from an SSD/slot/link problem?
I want to diagnose the cause rather than hide AER messages. I can provide sanitized pveversion -v, kernel command line and lspci output if useful.
Thank you.