AER: Corrected error received. Should I be worried?

[left4pve]

Sorry for the silly question. I'm seeing exactly the same error as in this post. My screen is flooded with this error with even no VM is running.

kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
kernel: nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
kernel: nvme 0000:01:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
kernel: nvme 0000:01:00.0: AER:    [ 0] RxErr

The derive of interest is: `01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/980PRO`

But I'm not seeing anything wrong with my desktop, even with heavy testing on read/write and checksum check. And I've never seen an uncorrectable error. So should I just let it be? Need some advice on professionals. Thanks.
Hardware:

1. Motherboard: Gigabyte z690i aorus ultra lite bios upgrade
2. CPU: Intel(R) Core(TM) i3-12100
3. Memory: Kingston 16GBx2
4. NVMe: Samsung 980Pro 2TB NVMe
5. Other disks: Samsung_SSD_850_EVO_1TB SSD + WDC_WD 16TB HDD

 

[dcsapak]

not sure if it's not just a red herring or some AER misconfiguration in the firmware itself

i have an ASUS Prime Z690-A here and i get very similar (but not identical) errors on boot:

kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0
kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
kernel: pcieport 0000:00:01.0:   device [8086:460d] error status/mask=00001000/00002000
kernel: pcieport 0000:00:01.0:    [12] Timeout

(in my case the id is that of a pcie port )

though they stop again (it's only a few) do you get them constantly?
you could try to upgrade the bios and/or playing around with AER settings in the bios (if there are such options)

maybe reseating the device or putting it in a different slot can help?

 

[left4pve]

@dscapak Upon some investigation, it might actually be related to the Samsung 980 Pro 2TB NVMe SSD I'm using? This model(as well as other Samsung NVMes) is notoriously bad for the 0E problem, which is confirmed on my machine with `smartctl`. I'm going to order another brand and see if the problem persists with a new installation of PVE. It'll arrive tomorrow.

 

[logiczny]

@dscapak Upon some investigation, it might actually be related to the Samsung 980 Pro 2TB NVMe SSD I'm using? This model(as well as other Samsung NVMes) is notoriously bad for the 0E problem, which is confirmed on my machine with `smartctl`. I'm going to order another brand and see if the problem persists with a new installation of PVE. It'll arrive tomorrow.

How it went? I'm getting same error, but have Samsung SSD 970 PRO 512GB. Not using iommu things to passthru GPU to VMs or other things like that.
I'm getting flooded with errors like this on my Dell laptop working as a proxmox server.

~ #: dmesg --follow
(...)
[  492.781326] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:06:00.0
[  492.781334] pcieport 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
[  492.781337] pcieport 0000:06:00.0:   device [8086:1576] error status/mask=00000080/00002000
[  492.781339] pcieport 0000:06:00.0:    [ 7] BadDLLP

~ #: uname -a
Linux proxmox5 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 GNU/Linux

~ #: lspci | grep 06
06:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]

~ #: lspci | grep "1d.6"
00:1d.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #15 (rev f1)