Bug 111601 - AER: Corrected error received: id=00e0
Summary: AER: Corrected error received: id=00e0
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_pci@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-31 13:40 UTC by Lev Lybin
Modified: 2018-02-01 16:45 UTC (History)
5 users (show)

See Also:
Kernel Version: 4.4
Tree: Mainline
Regression: No


Attachments
Marc Merlin 4.4.1 dmesg (102.79 KB, text/plain)
2016-02-15 17:13 UTC, Bjorn Helgaas
Details

Description Lev Lybin 2016-01-31 13:40:09 UTC
Reproduced not always, only after rebooting. If did shut down laptop, and run again - no problem, but if do reboot - can see errors again.

When I see problem:
[    0.223667] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.348402] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.505094] aer 0000:00:1c.0:pcie02: service driver aer loaded
[    0.505112] aer 0000:00:1c.3:pcie02: service driver aer loaded
[    0.505124] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[    0.505125] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    0.505127] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[    0.505132] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    0.505133] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    0.505135] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[    0.505140] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
[    0.505141] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[    0.505143] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
[    0.505151] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    3.647335] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[    3.647341] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[    3.647343] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[    3.647344] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[    3.901955] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[    3.901970] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[    3.904785] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[    3.907507] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[    7.389983] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[    7.390000] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[    7.390111] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[    7.390191] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[    7.390747] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[    7.390762] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[    7.390873] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00000001/00002000
[    7.390968] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)

00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) (prog-if 00 [Normal decode])
<------>Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
<------>Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
<------>Latency: 0
<------>Interrupt: pin A routed to IRQ 123
<------>Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
<------>I/O behind bridge: 0000f000-00000fff
<------>Memory behind bridge: df200000-df2fffff
<------>Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
<------>Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
<------>BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
<------><------>PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
<------>Capabilities: <access denied>
<------>Kernel driver in use: pcieport
<------>Kernel modules: shpchp


When no problem:

[    0.216986] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.338282] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.495196] aer 0000:00:1c.0:pcie02: service driver aer loaded
[    0.495214] aer 0000:00:1c.3:pcie02: service driver aer loaded
[    0.495227] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[    0.495228] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    0.495230] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[    0.495235] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    0.495236] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    0.495238] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[    0.495243] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
[    0.495244] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[    0.495246] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
[    0.495254] pciehp: PCI Express Hot Plug Controller Driver version: 0.4

00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) (prog-if 00 [Normal decode])
<------>Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
<------>Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
<------>Latency: 0
<------>Interrupt: pin A routed to IRQ 123
<------>Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
<------>I/O behind bridge: 0000f000-00000fff
<------>Memory behind bridge: df200000-df2fffff
<------>Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
<------>Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
<------>BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
<------><------>PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
<------>Capabilities: <access denied>
<------>Kernel driver in use: pcieport
<------>Kernel modules: shpchp

Kernel: 4.4.0-4-ARCH
Intel i7 6700HQ
MSI PE70 6QE
BIOS E1795IMS.10E 01/12/2016
microcode: CPU0 sig=0x506e3, pf=0x20, revision=0x55
GRUB_CMDLINE_LINUX_DEFAULT="elevator=noop intel_idle.max_cstate=7 nouveau.modeset=0"

I see a lot of these errors: https://www.google.co.th/search?q=AER%3A+Corrected+error+received%3A+id%3D00e0

It looks on this bug, but I just see these messages, no problems with boot: https://bugzilla.kernel.org/show_bug.cgi?id=109691
Comment 1 Bjorn Helgaas 2016-02-15 17:13:24 UTC
Created attachment 203701 [details]
Marc Merlin 4.4.1 dmesg

Marc Merlin reported what appears to be the same problem here:

  http://lkml.kernel.org/r/20160213215736.GA1002@merlins.org

I'm attaching the dmesg log he captured.

I suspect "pci=noaer" is a workaround (it disables AER completely).
Comment 2 Bjorn Helgaas 2016-07-15 22:43:38 UTC
Related report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588428/
Comment 3 Sebastiaan la Fleur 2016-08-12 08:41:18 UTC
Seems I get a very similar issue on my new Thinkpad P50 with the Arch linux kernel. No clue yet as to why, but I see two direct similarities:

- Intel i7 6700HQ
- Nvidia Quadro M1000M

I receive the same error message at boot everytime. Both with a new Arch linux install as well as the install image on kernel 4.6.1

I will be posting the complete dmesg log, however, a single difference is in the error message I receive. My AER corrected id=00e4.
Comment 4 Sebastiaan la Fleur 2016-08-12 08:48:54 UTC
Some more resources I found when googling the error:

https://bugzilla.kernel.org/show_bug.cgi?id=109691
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

The system with the issues has an Intel wifi chip but a realtek PCIe card reader. Will check to see if the connected PCIe device causing the errors is the card reader.
Comment 5 Sebastiaan la Fleur 2016-08-12 15:51:51 UTC
Disregard my previous messages. It seems it was a driver issue. After I reinstalled the nvidia and intel drivers, any error messages about AER were gone.

Note You need to log in before you can comment on or make changes to this bug.