Get spammed by PCIe Bus Error

[Pavel Moukhataev]

I'm spammed by PCIe Bus Error. I get this error 10 times per second in console. Error is:
pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) device [8086:a112] error status/mask=00000001/00000000
pcieport 0000:00:1c.0: [ 0] Receiver Error (First)

I collected some sys info:
lspci -vt>lspci_vt.log
lspci -nnv>lspci_nnv.log
lscpu>lscpu.log
cat /proc/cpuinfo >proc_cpuinfo.log
uname -a>uname_a.log
lshw>lshw.log
lsusb -v>lsusb_v.log
dmidecode>dmidecode.log
lsb_release -a>lsb_release.log
iwconfig >iwconfig.log

I run latest Ubuntu 17.04 on VivoBook Pro N752VX notebook (https://www.asus.com/Laptops/VivoBook-Pro-N752VX/specifications/).

This pcieport 1c.0 is connected to RTL8192EE PCIe Wireless Network Adapter (see lspci_vt.log).

I can disable this message by adding pci=nomsi kernel parameter, but this is not a bug fix, only a workaround. Also after appling this parameter wifi connection is quite slow and unstable. On windows 10 I get approx ping time 3ms to my wifi router. On Linux ping time is min/avg/max 5.548/60.137/261.145 with very good signal strength (see iwconfig.log).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-26-generic 4.10.0-26.30
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pmoukhataev 1907 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Jul 4 08:33:04 2017
InstallationDate: Installed on 2017-05-18 (46 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. N752VX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=1365c792-1a17-47ad-8c37-f738d0645d3d ro nosplash pci=nomsi
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-26-generic N/A
 linux-backports-modules-4.10.0-26-generic N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N752VX.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N752VX
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.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N752VX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Joseph Salisbury (jsalisbury)]

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.12 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.12

[Pavel Moukhataev (m-pashka)]

Issue happened on newly installed ubuntu 17.04. Since installation my kernel was upgraded several times. Bug is present in all kernel versions.

It seems kernel-ppa was not built properly for ubuntu 17.04 zesty release:

E: The repository 'http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu zesty Release' does not have a Release file.

[Pavel Moukhataev (m-pashka)]

Installed kernel 4.12 (4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64), problem still remains.