I just noticed a persistent issue in my log showing up in red (snip shown below).  This occurred about 10 times a second 15 min straight.  Some background data on my system.  About 2 weeks ago I moved from an intel box to an AMD box. I simply moved the drives over along with the undraid thumb stick.   Any ideas?

 

 

Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00000040/00006000
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1:    [ 6] BadTLP                
Mar 27 14:11:24 tower kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:00:00.0
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00000040/00006000
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1:    [ 6] BadTLP                
Mar 27 14:11:24 tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 27 14:11:24 tower kernel: pcieport 0000:00:01.3:   device [1022:1453] error status/mask=00000040/00006000
Mar 27 14:11:24 tower kernel: pcieport 0000:00:01.3:    [ 6] BadTLP                
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 27 14:11:24 tower kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00000040/000060

 

Edited March 29, 20206 yr by dubbly
Resolved Issue

jbarlett had the same problem with his X399 motherboard in the past and the fix was to update BIOS.

Alternatively, adding pci=nommconf to sysconfig also helped hide the errors but updating BIOS was the perm fix.

Those errors are harmless (since they are corrected) other than filling up the syslog.

 

Source:

 

Thank you. Good to know that they are harmless. I have an x370 motherboard and the bios is updated as far as I can.  Warnings not to update it to the next version unless I have the latest generation AMD CPU and i have a 2700x.  

I've suddenly started getting these errors on my x99 chipset motherboard. Server is working fine as far as I can tell though.

 

Mine is complaining about device [8086:6f02] which refers to "00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)".

 

Assuming that this refers to PCI-E slot 1 which had a graphics card I've tried moving it to a different slow but error is still appearing, albeit nowhere near as a frequently.

 

I'm wondering if a docker update could somehow introduce this error as nothing has changed hardware wise.

34 minutes ago, allanp81 said:

I'm wondering if a docker update could somehow introduce this error as nothing has changed hardware wise.

No. Docker update shouldn't introduce the error.

You could be having it all along but the devices are not being used in a way that would cause those messages to show up.

 

As long as it says "error corrected", those are harmless.

As I said above, try adding pci=nommconf to syslinux to hide the errors so they don't fill up your syslog.

Just wondering why people seem to get these errors all of a sudden. The errors do say Corrected though.

I am using the X399 motherboard, and have updated to the latest BIOS. I have also disabled ASPM in the BIOS, and also added pci=nommconf to syslinux. I am still receiving these errors every second. Does anyone have any other ideas?

7 hours ago, PhantamaroK said:

I am using the X399 motherboard, and have updated to the latest BIOS. I have also disabled ASPM in the BIOS, and also added pci=nommconf to syslinux. I am still receiving these errors every second. Does anyone have any other ideas?

You should identify which PCIe bus and device got those error then try to replug it or change to other slot, if not help, try boot unraid in safe mode and check again.

 

PS, post have make solve, pls start new own post.

Edited April 29, 20206 yr by Benson