35 GB/day of "PCIe Bus Error: severity=Corrected, type=Data Link Layer..." in syslog

  • Ubuntu 20.04.4 LTS
  • Dell XPS 8940
  • latest BIOS 2.4.0

New install, and system seems to be working fine, but I have 35 gigs/day of syslog error messages like:

Feb 25 00:00:10 mumsilar kernel: [32409.088886] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Feb 25 00:00:10 mumsilar kernel: [32409.088907] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Feb 25 00:00:10 mumsilar kernel: [32409.088908] pcieport 0000:00:01.0: device [8086:4c01] error status/mask=00000040/00002000
Feb 25 00:00:10 mumsilar kernel: [32409.088910] pcieport 0000:00:01.0: [ 6] BadTLP
Feb 25 00:00:19 mumsilar kernel: [32418.024062] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Feb 25 00:00:19 mumsilar kernel: [32418.024100] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 25 00:00:19 mumsilar kernel: [32418.024102] pcieport 0000:00:01.0: device [8086:4c01] error status/mask=00000001/00002000
Feb 25 00:00:19 mumsilar kernel: [32418.024103] pcieport 0000:00:01.0: [ 0] RxErr
Feb 25 00:00:20 mumsilar kernel: [32418.431966] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Feb 25 00:00:20 mumsilar kernel: [32418.432012] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 25 00:00:20 mumsilar kernel: [32418.432014] pcieport 0000:00:01.0: device [8086:4c01] error status/mask=00000001/00002000
Feb 25 00:00:20 mumsilar kernel: [32418.432016] pcieport 0000:00:01.0: [ 0] RxErr
Feb 25 00:00:20 mumsilar kernel: [32418.443484] pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0
Feb 25 00:00:20 mumsilar kernel: [32418.443492] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Feb 25 00:00:20 mumsilar kernel: [32418.443494] pcieport 0000:00:01.0: device [8086:4c01] error status/mask=00000040/00002000
Feb 25 00:00:20 mumsilar kernel: [32418.443495] pcieport 0000:00:01.0: [ 6] BadTLP
...

Here is the output of the following commands

sudo lspci -nn
sudo lspci -tv
sudo lshw -C network
sudo sysctl vm.swappiness
inxi -Fxxxrz
sudo lspci -s 00:01.0 -vvv

(added lspci -s 00:01.0 -vvv output)

Thanks for any help you can give. Cheers.

P.S.

I had added this one line to /etc/modprobe.d/alsa-base.conf

# apparently after power saving shuts down the audio, the next time it turns on
# it will audibly pop. Turn off shutting down the audio to prevent the popping.
# see
options snd-hda-intel power_save=0 power_save_controller=N
8

1 Answer

It looks like your Nvidia card is causing the syslog problem.


Feb 25 00:00:10 mumsilar kernel: [32409.088886] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Feb 25 00:00:10 mumsilar kernel: [32409.088907] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Feb 25 00:00:10 mumsilar kernel: [32409.088908] pcieport 0000:00:01.0: device [8086:4c01] error status/mask=00000040/00002000

00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:4c01] (rev 01)

-[0000:00]-+-00.0-[ff]-- +-01.0-[02]--+-00.0 NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] | +-00.1 NVIDIA Corporation TU116 High Definition Audio Controller | +-00.2 NVIDIA Corporation TU116 USB 3.1 Host Controller | \-00.3 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER]

Try Nvidia 510.54. Try a different video card, if you can get access to one.

To quiet the syslog noise, do this...

sudo -H gedit /etc/default/grub # edit this file

Find:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Change it to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"

Save the file.

sudo update-grub # update GRUB

reboot # reboot the computer

Update #1:

Fixed by turning off ASPM: pcie_aspm=off

1

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like