Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

Bug #1687714 reported by Dmitrii Shcherbakov
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned
Xenial
Triaged
Medium
Unassigned
Zesty
Triaged
Medium
Unassigned
Artful
Triaged
Medium
Unassigned

Bug Description

The kernel log is constantly filled with the following:

  236.912499] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 236.912545] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)
[ 236.912553] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00001000/00002000
[ 236.912558] pcieport 0000:00:1c.5: [12] Replay Timer Timeout

This drains battery, CPU cycles and makes the kernel log unreadable.

Adding pcie_aspm hides that:

GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open pcie_aspm=off"

Present in the upstream Linux kernel (see the attachment for 4.11 rc8).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gdm 2345 F.... pulseaudio
                      dima 4262 F.... pulseaudio
Date: Tue May 2 13:34:13 2017
InstallationDate: Installed on 2017-02-27 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd
 Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Razer Blade
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet button.lid_init_state=open
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Razer
dmi.bios.version: 1.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.name: Blade
dmi.product.version: 6.06
dmi.sys.vendor: Razer

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux (Ubuntu Zesty):
importance: Undecided → Medium
status: New → Incomplete
tags: added: kernel-da-key
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

Hi Joseph,

Not a regression. I installed Zesty while it was in beta on this machine and an issue was there already.

Tried 4.8 on a live usb - had that issue as well.

This is a relatively new hw so 4.4 kernel was not possible to boot properly.

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

Reproduced on 4.8-36-generic (the log has rotated due to the volume of messages so the kernel version message is not there).

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

Reproduced on 4.8-36-generic (the log has rotated due to the volume of messages so the kernel version message is not there).

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in linux (Ubuntu Zesty):
status: Incomplete → Triaged
Changed in linux (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.