52

I have Ubuntu 16.10 (although the same happened on 16.04) on a dual boot with Windows 10. I noticed some time ago that my kern.log file was getting pretty big (10GB or more) so I decided to check it. The same error seems to be repeating every second or less:

Dec 19 17:31:01 andrew kernel: [   99.027473] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 19 17:31:01 andrew kernel: [   99.027474] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Dec 19 17:31:01 andrew kernel: [   99.027475] pcieport 0000:00:1c.5:    [ 0] Receiver Error        
Dec 19 17:31:01 andrew kernel: [   99.027479] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 19 17:31:01 andrew kernel: [   99.027826] pcieport 0000:00:1c.5: can't find device of ID00e5
Dec 19 17:31:01 andrew kernel: [   99.027887] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5

I have tried adding to the grub pci=nomsi and pci=noaer but it keeps popping up. I am using a ASUS Laptop with an Nvidia Geforce 920M. Maybe that's the reason?

Scott Stensland
  • 15,575
Andrew
  • 634
  • I found this error on same device [8086:9d15] : Intel Corporation Sunrise Point-LP PCI Express Root Port This is an ASUS X541UV laptop. I had latest BIOS update (3.09) Just for the record. I had found this bug that seems related to this issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 – cheche Jul 24 '22 at 11:09

8 Answers8

48

I believe this may be due to PCIe Active State Power Management that is transitioning the link to a lower power state and maybe causing the device to trigger these errors. I believe the device in question is the Sunrise Point-LP PCI Express Root Port.

Try using the pcie_aspm=off boot parameter to see if this stops the messages. Note that this will increase the power consumption of your machine as it disables the power savings.

Colin Ian King
  • 18,820
  • In my case I noticed it because systemd-journal caused high cpu usage. Adding the parameter helped. I read however, that this disables some energy saving measures. Probably all for PCIe devices (?) – Zelphir Kaltstahl Feb 10 '17 at 00:10
  • 3
    pcie_aspm=off does indeed disable PCIe power savings. There are in fact two savings modes: L0s and L1 mode. L0 uses low power mode for one direction of the PCIe serial link only. L1 is bidirectional, resulting in improved power reduction (but does incur higher startup latencies). – Colin Ian King Feb 10 '17 at 00:17
  • see https://askubuntu.com/questions/271058/add-ro-quiet-splash-to-all-entries – Ferroao Jun 30 '17 at 18:54
  • 1
    I believe this is the best answer. pci=nomsi disables some interrupts and noaer just disables error reporting, not the actual problem. See also https://askubuntu.com/a/1066030/284929 – wbkang Dec 20 '18 at 03:43
  • 1
    Same error with Debian, problem solved by this answer – Thecave3 Jul 07 '19 at 17:59
  • If this will cause the system to use more power and making the battery life shorter so isn't it a bad idea to turn the asmp off?? and maybe it's better to just ignore the errors that are referring to something actually has no harm for the system and turn the error logs off. – Amir Mar 28 '20 at 20:59
  • This worked for me on Fedora 32. Performance of my Intel card also increased dramatically. From pings in the 40ms-130ms range in my local network to 2ms-4ms. Linux, man.. – Aspiring Dev May 01 '20 at 15:43
  • I encountered this problem today. The solution does appear to work, but you may be able to fix the problem with aspm in your bios and leave it on (assuming you care.) When I narrowed my issue down to this I went into my bios and found that aspm was off everywhere, when I turned it on the errors went away without the need to disable aspm in the kernel... at least for now. – David Oldford Nov 03 '20 at 13:03
  • Solved same or very similar problem on my Ubuntu 20.04.2 LTS on a HP Pavillion laptop. Log was growing like crazy, and every reboot took more than 30" to 1 minute just logrotating it. Processor load was not notorious. Previously installed Linux Mint ran very slow in comparison, with high CPU loads related to the same condition. – David Ramirez Mar 10 '21 at 06:25
  • Had the same on a dual-boot Dell XPS 15 running Ubuntu 20.04. In my case the device was the SSD. The answer above fixed it for me. – Fanta Oct 09 '21 at 13:19
  • Same error on an Odroid H3 with an NVMe SSD; "official" recommendation is to update BIOS, this made the errors disappear as well – Tomáš M. Feb 06 '23 at 16:50
  • Hi all, how to set this pcie_aspm=off. Do I need to edit any file or just run it in terminal – S Andrew Apr 06 '23 at 15:30
  • I literally went to lunch, when I came back, "Hard Drive full" alerts everywhere.... Worked great. Anyone wandering how to set this parameter see this link: https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter – Bruno Polo Jul 31 '23 at 18:44
15

Try these steps:

  1. sudo gedit /etc/default/grub

  2. Edit grub. Add pci=noaer at the end of GRUB_CMDLINE_LINUX_DEFAULT. Line will be like this:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"

  3. sudo update-grub

  4. Reboot now

:) Enjoy.

CentaurusA
  • 2,672
Ehtesham
  • 159
11

I had the same problem, but the solution was to add pci=nomsi to /etc/default/grub file. Perform the following edit:

before:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

after:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"

And save the settings:

sudo update-grub
David Foerster
  • 36,264
  • 56
  • 94
  • 147
Roozbeh Zabihollahi
  • 221
  • 2
  • 5
7

  1. If you already installed Ubuntu or Mint, just go to the GRUB screen and from there go to recovery mode. Then go to root and make the commands like on the video and from there make the changes again like in the video, but if pci=nomsi/pci=noaer does not work for you, change it to pcie_aspm=off.

  2. If you cannot install the OS because of this problem, you can edit the boot order in GRUB. You can do that when you boot up for a installation but instead of pressing Enter press E to edit. There should be a line named Linux. Add at the end pcie_aspm=off, but also try out pci=nomsi/pci=noaer.

    Remember, though, that this is not a permanent fix. To fix it permanently apply step 1 after installation. Also, do not forget to update GRUB.

BeastOfCaerbannog
  • 14,585
Bossy 0202
  • 71
3

I was installing Debian 11, kernel 5.10 amd64. I was getting similar error. During booting, I pressed escape to get boot: prompt At prompt wrote install pcie_aspm=off It worked.

ShaileshKumarMPatel
  • 11
2

I installed Ubuntu 18.04 today and I noticed the same problem. I've just installed that package and problem has been solved.

sudo apt-get install busybox-syslogd

Check log files size and do empty large files:

ls -s -S /var/log

result:

total 4352668
4021088 syslog                 32 wtmp                  4 gdm3
 329168 kern.log               24 Xorg.0.log            4 hp
   1776 dpkg.log               20 Xorg.1.log            4 installer
     40 lastlog                20 Xorg.0.log.old        4 journal

and do:

cd /var/log
sudo su
$ > syslog
$ > kern.log

Then, to make sure, let follow this answer above https://askubuntu.com/a/1019225/725320

In case you can't boot into Ubuntu and get stuck with these logs in your screen (same as me):

Dec 19 17:31:01 andrew kernel: [   99.027473] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 19 17:31:01 andrew kernel: [   99.027474] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Dec 19 17:31:01 andrew kernel: [   99.027475] pcieport 0000:00:1c.5:    [ 0] Receiver Error        
Dec 19 17:31:01 andrew kernel: [   99.027479] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 19 17:31:01 andrew kernel: [   99.027826] pcieport 0000:00:1c.5: can't find device of ID00e5
Dec 19 17:31:01 andrew kernel: [   99.027887] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
  • Use Recovery Mode to get root shell
  • Do empty large log files
  • Boot into Ubuntu, install busybox-syslogd and update grub config
Thế Ngọc Phan
  • 21
1

Bug was gone (fixed, I think) in my PC today after installing new Kernel version "linux-image-4.15.0-50-generic" in Ubuntu 18.04.2 x86_64.

Pebas
  • 111
1

ASUS G20. Ran this error message 10000 times or so on startup and closing. Easy Fix, in BIOS, Advanced, I changed PCI Express native power management to disabled. And I'm just beginning to aspire to beginner status.

tom
  • 11