kernel-packages team mailing list archive

[David Henningsson <1521173@xxxxxxxxxxxxxxxxxx>]

Hi,

Indeed booting with pci=noaer (as suggested in the other bug) works 
around this issue as well. I'll use that for the time being.

Thanks for working on it!

// David

On 2015-12-29 16:58, Bjorn Helgaas wrote:
> 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.
>
> This is a pretty obvious bug in our AER code.  We normally clear
> correctable errors by writing the PCI_ERR_COR_STATUS register in
> handle_error_source().  The execution path looks like this:
>
>    aer_isr_one_error
>      aer_print_port_info
>      if (find_source_device())
>        aer_process_err_devices
>          handle_error_source
>            pci_write_config_dword(dev, PCI_ERR_COR_STATUS, ...)
>
> In this case, find_source_device() printed "can't find device of
> ID00e0" [sic] and returned false, so we don't call
> aer_process_err_devices().  The error is never cleared, so
> we discover it again and again.
>
> I'll work on fixing this.  Incidentally, there's another report
> with similar symptoms here:
>
>    https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
> Bjorn
>

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic


** Bug watch added: Linux Kernel Bug Tracker #109691
   http://bugzilla.kernel.org/show_bug.cgi?id=109691

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521173

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport 0000:00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport 0000:00:1c.0:   device [8086:9d14] error status/mask=00000001/00002000
  [ 5315.995683] pcieport 0000:00:1c.0:    [ 0] Receiver Error        
  [ 5316.002772] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport 0000:00:1c.0:   device [8086:9d14] error status/mask=00000001/00002000
  [ 5316.002838] pcieport 0000:00:1c.0:    [ 0] Receiver Error        
  [ 5316.009926] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport 0000:00:1c.0:   device [8086:9d14] error status/mask=00000001/00002000
  [ 5316.009991] pcieport 0000:00:1c.0:    [ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david      1502 F...m pulseaudio
   /dev/snd/controlC0:  david      1502 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware                            1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions