exist2resist Posted July 8, 2021 Share Posted July 8, 2021 (edited) Put in a new CPU into my X99 board a few weeks ago and I keep getting these PCIE errors. Quote Jul 4 06:37:41 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 06:37:41 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 06:37:41 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.2: AER: Corrected error received: 0000:00:02.2 Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 06:37:54 Tower kernel: pcieport 0000:00:02.2: device [8086:6f06] error status/mask=00000001/00002000 Jul 4 07:15:37 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 07:15:37 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:15:37 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 07:32:47 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 07:32:47 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:32:47 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.2: AER: Corrected error received: 0000:00:02.2 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.2: device [8086:6f06] error status/mask=00000001/00002000 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:36:19 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 07:36:19 Tower kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:36:19 Tower kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000001/00002000 Jul 4 07:45:30 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 07:45:30 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 07:45:30 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 09:16:16 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Jul 4 09:16:16 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 09:16:16 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 09:25:35 Tower kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Jul 4 09:25:35 Tower kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 09:25:35 Tower kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000001/00002000 Jul 4 09:27:15 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 09:27:15 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 09:27:15 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 09:36:14 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Jul 4 09:36:14 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 09:36:14 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 09:37:39 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 09:37:39 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 09:37:39 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 10:06:03 Tower kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Jul 4 10:06:03 Tower kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:06:03 Tower kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000001/00002000 Jul 4 10:07:07 Tower kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0 Jul 4 10:07:07 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Jul 4 10:07:07 Tower kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:07:07 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:07:07 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 10:07:07 Tower kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000001/00002000 Jul 4 10:36:02 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 10:36:02 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:36:02 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 10:45:33 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 10:45:33 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:45:33 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 10:58:23 Tower kernel: pcieport 0000:00:02.2: AER: Corrected error received: 0000:00:02.2 Jul 4 10:58:23 Tower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 10:58:23 Tower kernel: pcieport 0000:00:02.2: device [8086:6f06] error status/mask=00000001/00002000 Jul 4 11:21:21 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 11:21:21 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 11:21:21 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.2: AER: Multiple Corrected error received: 0000:00:02.2 Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 11:30:30 Tower kernel: pcieport 0000:00:02.2: device [8086:6f06] error status/mask=00000001/00002000 Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.2: AER: Multiple Corrected error received: 0000:00:02.2 Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.2: device [8086:6f06] error status/mask=00000001/00002000 Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 4 12:12:48 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000001/00002000 Jul 4 12:12:51 Tower kernel: pcieport 0000:00:02.0: AER: Corrected error received: 0000:00:02.0 The Devices the error references are as follows: Quote IOMMU group 29:[8086:6f02] 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) IOMMU group 30:[8086:6f04] 00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) IOMMU group 31:[8086:6f06] 00:02.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) IOMMU group 32:[8086:6f08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) Edited July 13, 2021 by exist2resist Solution Quote Link to comment
exist2resist Posted July 8, 2021 Author Share Posted July 8, 2021 (edited) Fond this article: With this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 Edited July 8, 2021 by exist2resist Quote Link to comment
arturovf Posted July 8, 2021 Share Posted July 8, 2021 I do have those kind of errors in my log since long time ago, which seems to be harmless since they say corrected. I tried to hide the errors with some commands suggested here in the forums with no success. Quote Link to comment
ich777 Posted July 8, 2021 Share Posted July 8, 2021 @exist2resist & @arturovf add this to your syslinux configuration: 1 2 Quote Link to comment
arturovf Posted July 8, 2021 Share Posted July 8, 2021 3 minutes ago, ich777 said: @exist2resist & @arturovf add this to your syslinux configuration: it worked, THANK YOU! 1 Quote Link to comment
ich777 Posted July 8, 2021 Share Posted July 8, 2021 5 minutes ago, arturovf said: it worked, THANK YOU! Btw, this shouldn't harm anything since the PCIe cards and also the Motherboard itself should handle everything, my Motherboard also has the same issue and if I don't turn off AER then the TV Steam from my DigitalDevices DVB-C cards are getting really trashed and my syslog is spammed with those messages. 1 Quote Link to comment
exist2resist Posted July 13, 2021 Author Share Posted July 13, 2021 On 7/8/2021 at 12:00 PM, ich777 said: @exist2resist & @arturovf add this to your syslinux configuration: That did the trick, thanks. I was going to check and turn it off in BIOS, but that is a bit easier. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.