You are not logged in.
Hello. It's not always happening but more often than not when I restart my laptop or shut it down I get a spamming error that says:
[ 63.009521] pcireport 0000:00:1d.3: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 63.010431] pcireport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
[ 63.011334] pcireport 0000:00:1d.3: AER: [ 0] RxErr [First]
my 'lspci -nnk' gives the following output:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [103c:8216]
Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)
DeviceName: Intel Kabylake HD Graphics ULT GT2
Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8216]
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [103c:8216]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP USB 3.0 xHCI Controller [103c:8216]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP Thermal subsystem [103c:8216]
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP CSME HECI [103c:8216]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP SATA Controller [AHCI mode] [103c:8216]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1)
Kernel driver in use: pcieport
00:1d.3 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d58] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP LPC Controller [103c:8216]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP PMC [103c:8216]
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio [103c:8216]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP SMBus [103c:8216]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940MX] [10de:134d] (rev a2)
DeviceName: NVIDIA N16S-GTR
Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8216]
Kernel modules: nouveau, nvidia_drm, nvidia
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
Subsystem: Hewlett-Packard Company RTS522A PCI Express Card Reader [103c:8216]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller [103c:8216]
Kernel driver in use: r8169
Kernel modules: r8169
05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:81c1]
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Last edited by FunkyPuppy (2020-05-14 15:45:09)
Offline
Please wrap those in [ code ] [ /code ] tags without the spaces.
Post
lspci -nnk
(and/or post the actual error message unedited and untruncated, as that would include businformation in most cases) so we can actually use that vendor information of the error message to get the culprit device, due to their buggy nature I'm guessing the realtek wifi controller. Generally if these errors really only happen during shutdown and do just list "Severity:Corrected" then this behaviour can be normal to a degree and not necessarily cause for worry.
Last edited by V1del (2020-05-14 15:39:43)
Offline
Is this better? I am sorry for any mistakes, I read most of the code of conduct but I haven't really posted here before. Thanks for the help in advance. As you can see I have edited the first message in the post to include the whole error message and i have now posted the output of "lspci -nnk".
Last edited by FunkyPuppy (2020-05-14 15:48:27)
Offline
Thanks much better, not entirely conclusive which real device if any yet. We might need some more context on when the error happens, do they even show up in the journal? After rebooting from such a faulty situation what does your
sudo journalctl -b-1
look like?
Offline
To answer the first part, I don't really know what causes the error. It only happens when I restart or shut down my laptop and sometimes (not every time) i even get a message
Journal Failed to Start
For the second part, when I try out the command sudo journalctl -b-1 I get the following message:
Data from the specified boot (-1) is not available: No such boot ID in journal
but when I try sudo journalctl -b i get this :
-- Logs begin at Thu 2020-05-14 18:41:26 EEST, end at Thu 2020-05-14 18:50:08 EEST. --
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 2171 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 23 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 15 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 15 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 15 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: device [8086:9d1b] error status/mask=00000001/00002000
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Multiple Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 23 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 23 kernel messages
Μαΐ 14 18:41:26 csakou-hppavilionnotebook kernel: pcieport 0000:00:1d.3: AER: Corrected error received: 0000:00:1d.3
Μαΐ 14 18:41:26 csakou-hppavilionnotebook systemd-journald[2505]: Missed 19 kernel messages
Offline
I'm more interested in the messages preceding the error spam. But it does look like this is just some weird unconnected bus that pushes out messages when it gets/loses power. I'd say try a BIOS/UEFI update, if you just want to hide the messages you could also add
pci=noaer
to your kernel parameters, but that has the potential to hide real bus errors as well.
Offline
Hello again. So I did as you instructed and updated my BIOS/UEFI but I did it from within Windows as it seemed easier and my previous problem doesn't show up at this point in time so it might have worked! Now though after the update, BIOS/UEFI can no longer see Manjaro as a boot option (or Grub in that sense since it says Manjaro but it actually boots to Grub) but when I go to boot options in BIOS/UEFI it has an option to find EFI file and from there I can find the boot file and start Grub normally. How do I make grub known to the BIOS/UEFI again?
Last edited by FunkyPuppy (2020-05-14 18:14:10)
Offline
Offline
Ok I managed to create an entry for grub without reinstalling anything and it works fine. The bad news is that the previous PCIe Error I was getting still persists. I will try installing a different kernel and see if the problem keeps on existing.
Edit: Now system-journal is constantly using 100% of a cpu core to spam write into journalctl the same error message I posted at the beginning. Is there anything I can do?
Last edited by FunkyPuppy (2020-05-14 21:58:36)
Offline
"pcie_aspm=off" kernel parameter fixes that.
Offline