Logs flooded with "AER: Multiple Corrected error received: 0000:00:01.0"

[notarobot]

Hi everyone,

I have a problem on my new Proxmox server. The logs are flooded with these lines:

Oct  3 19:22:42 proxmox kernel: [   99.530012] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct  3 19:22:42 proxmox kernel: [   99.530016] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Oct  3 19:22:42 proxmox kernel: [   99.530164] pcieport 0000:00:01.0:   device [8086:1901] error status/mask=00001000/00002000
Oct  3 19:22:42 proxmox kernel: [   99.531022] pcieport 0000:00:01.0:    [12] Timeout

when I do lspci -v I can see that 00:01.0 is:

00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0, IRQ 121
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    I/O behind bridge: 0000e000-0000efff
    Memory behind bridge: de000000-df0fffff
    Prefetchable memory behind bridge: 00000000c0000000-00000000d1ffffff
    Capabilities: [88] Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)
    Capabilities: [80] Power Management version 3
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [a0] Express Root Port (Slot+), MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [140] Root Complex Link
    Capabilities: [1c0] Advanced Error Reporting
    Capabilities: [d94] #19
    Kernel driver in use: pcieport

Anyone know the reason of these errors and how I can solve them ?

Thanks for your help !

 

[Alwin]

Check for BIOS/firmware and microcode updates.

To just silence the AER, see the launchpad [0] entry. The documentation to AER can be found on kernel.org [1].

[0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173
[1] https://www.kernel.org/doc/Documentation/PCI/pcieaer-howto.txt

 

[notarobot]

I've "solved" it by editing /etc/default/grub
and in GRUB_CMDLINE_LINUX_DEFAULT I added pci=nommconf and I no longer have the issue.

Is it recommended and safe ?

 

[Alwin]

Is it recommended and safe ?

Can't say, but the LWN [0] seems to agree, that not many devices are needing the extra config space.
https://lwn.net/Articles/263288/

 

[theblinkingusb]

Also had this issue on a 2tb Samsung 980 pro + old i7-8550
Was able to do the above edit by notarobot and also run update-grub
Believe this is due to pcie generational issues from 3 to 4? Not 100% sure - additional info