On Wed, Sep 2, 2015 at 5:01 PM, Daniel Drake <drake@xxxxxxxxxxxx> wrote: > Hi, > > Working with a sample for a new laptop based on Intel Skylake, the > kernel logs are full of these messages: > > pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5 > pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, > type=Physical Layer, id=00e5(Receiver ID) > pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000 > pcieport 0000:00:1c.5: [ 0] Receiver Error (First) > pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5 > pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, > type=Physical Layer, id=00e5(Receiver ID) > pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000 > pcieport 0000:00:1c.5: [ 0] Receiver Error (First) > pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5 > pcieport 0000:00:1c.5: can't find device of ID00e5 > > Reproduced on 4.2 and on linus master as of today, using x86_64_defconfig. > > Apart from the log spam, there is no user-visible effect that I'm > aware of. Booting with pci=nomsi makes the messages go away. > > Any thoughts, is this something worth looking into in more detail? > > full dmesg: https://gist.github.com/dsd/1d7f738e917465edf2ae > lspci dump: https://gist.github.com/dsd/dc2481d64aadd520b0b3 Thanks, Daniel, this is indeed really annoying and worth looking into. Do you happen to know whether it's a regression? We haven't changed much in AER recently, but it's possible we broke something. Even if it's not a regression, the output seems a bit wordy and redundant. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
