AER, advanced error reporting[1], is generated by hardware and corrected
AERs usually doesn't mean any harm because they're just notifications to
upper OS that some minor errors like CRC has been corrected
automatically by hardware. There is little you can do but to turn off
such reporting by append kernel boot parameter "noaer".

[1]: https://www.kernel.org/doc/html/latest/PCI/pcieaer-howto.html

** Changed in: linux (Ubuntu)
       Status: New => Invalid

-- 
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/1859429

Title:
  Boot took much longer with repeated error message PCIe Bus Error:
  severity=Corrected, type=Data Link Layer, (Transmitter ID)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I saw this message in several other bugs but I am using the newest kernel. 
Right after upgrade the kernel the boot took several minutes and a message was 
being repeated several times in screen:
  [  340.489762] pcieport 0000:00:1c.5: AER: Corrected error received: 
0000:00:1c.5
  [  340.489775] pcieport 0000:00:1c.5: AER: PCIe Bus Error: 
severity=Corrected, type=Data Link Layer, (Transmitter ID)
  [  340.489780] pcieport 0000:00:1c.5: AER:   device [8086:9d15] error 
status/mask=00001000/00002000
  [  340.489784] pcieport 0000:00:1c.5: AER:    [12] Timeout  


  The notebook didn't had an issue so far and uptime is 35 minutes. I
  don't see any issue on performance as of now. All partitions are
  present.

  Before this event of slow down in boot (and notebook frozen for a few
  seconds duing boot) I was having this same message once or twice and
  then it was normal boot.

  
  root@dell-ubuntu:~# cat /proc/version
  Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 
20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019
  root@dell-ubuntu:~# cat /proc/version_signature 
  Ubuntu 5.3.0-26.28-generic 5.3.13
  root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd
  Description:  Ubuntu 19.10
  Release:      19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  gdm        3886 F.... pulseaudio
                        billmask   4450 F.... pulseaudio
  Date: Mon Jan 13 08:00:06 2020
  InstallationDate: Installed on 2019-07-28 (169 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 7572
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vg_root-lv_root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware                            1.183.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (80 days ago)
  dmi.bios.date: 05/31/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 082HPJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd05/31/2019:svnDellInc.:pnInspiron7572:pvr:rvnDellInc.:rn082HPJ:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7572
  dmi.product.sku: 0829
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to