Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)

[Srikanth]

Ubuntu 16.04 LTS ASUS R558U.

Similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979

I find repeated error/Logs in all virtual consoles, because of which I can't work in the virtual consoles. I am not using nvidia proprietary drivers.

Below is the error/log printed (Pasted from dmesg)

[ 1431.552877] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
[ 1431.553286] pcieport 0000:00:1c.5: can't find device of ID00e5
[ 1431.553304] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 1431.553321] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[ 1431.553330] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
[ 1431.553339] pcieport 0000:00:1c.5: [ 0] Receiver Error

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nova 3697 F.... pulseaudio
CRDA:
 country IN: DFS-JP
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5170 - 5250 @ 80), (N/A, 20), (N/A)
  (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
  (5735 - 5835 @ 80), (N/A, 20), (N/A)
CurrentDesktop: Unity
Date: Sun Aug 7 22:31:46 2016
HibernationDevice: RESUME=UUID=1e323818-6a1a-4387-9d9e-309fbfd07949
InstallationDate: Installed on 2016-07-16 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X556UF
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=169951e0-8588-4ed4-8b79-8c247c4aee05 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UF.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X556UF
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UF.206:bd09/10/2015:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X556UF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-07-16 (25 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.4.14-040414-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 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.8-rc1

[Srikanth (srikanths1010)]

apport information

[Srikanth (srikanths1010)]

apport information

[Srikanth (srikanths1010)]

Well this is a new System, so I can't be sure if this was working in previous releases.

The issue exists in Mainline kernel too.

Have tested with these packages,

linux-headers-4.4.14-040414_4.4.14-040414.201606241434_all.deb
linux-headers-4.4.14-040414-generic_4.4.14-040414.201606241434_amd64.deb
linux-image-4.4.14-040414-generic_4.4.14-040414.201606241434_amd64.deb

[penalvch (penalvch)]

Srikanth, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Srikanth (srikanths1010)]

Thank you for the detailed information,

I have tested with most recent kernel, following the URL provided above. The problem still exists. Below are the kernel version I've tested with.

linux-headers-4.8.0-040800rc4_4.8.0-040800rc4.201608312129_all.deb
linux-image-4.8.0-040800rc4-generic_4.8.0-040800rc4.201608312129_amd64.deb
linux-headers-4.8.0-040800rc4-generic_4.8.0-040800rc4.201608312129_amd64.deb

[Srikanth (srikanths1010)]

After updating the bios version to 405. The problem still exists.

Output of `sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date`

X556UF.405
06/28/2016

[penalvch (penalvch)]

Srikanth, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Bjorn Helgaas, Dan Zink, Greg Kroah-Hartman, and Dely Sy CC linux-pci)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.