From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.136]:43376 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752433AbbLVV6D (ORCPT ); Tue, 22 Dec 2015 16:58:03 -0500 Date: Tue, 22 Dec 2015 15:57:58 -0600 From: Bjorn Helgaas To: David Henningsson Cc: linux-pci@vger.kernel.org, bhelgaas@google.com Subject: Re: Dmesg filled with "AER: Corrected error received" Message-ID: <20151222215758.GA17235@localhost> References: <5673E049.2010704@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <5673E049.2010704@canonical.com> Sender: linux-pci-owner@vger.kernel.org List-ID: Hi David, On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote: > Hi Linux PCI maintainers, > > My dmesg gets filled with a few lines repeated over and over again: > > pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0 > pcieport 0000:00:1c.0: can't find device of ID00e0 > pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0 > pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, > type=Physical Layer, id=00e0(Receiver ID) > pcieport 0000:00:1c.0: device [8086:9d14] error > status/mask=00000001/00002000 > pcieport 0000:00:1c.0: [ 0] Receiver Error > > This happens 10-30 times per second (!), so dmesg fills up quickly. > The bug is present in both vanilla and Ubuntu kernels. > > I'm happy to try to help by providing more info as requested, and > I'm also able to build kernels to test patches (although that might > take some time, especially during the upcoming holidays). > > Computer: Dell Inspiron 13-7359 > Kernel version: Linux version 4.4.0-040400rc5-generic (kernel@gloin) > (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201512140221 > SMP Mon Dec 14 02:23:36 UTC 2015 > CPU: Skylake i3-6100U > Lspci: attached > Dmesg: I'm attaching an extract from kern.log which shows the most > recent boot and a few seconds thereafter. > Downstream bug report: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 Thanks a lot for the report and logs. Do you happen to know whether this is a regression, and if so, when it first appeared? Bjorn