Frequent PCIe bus error on device 8086:a292

Bug #1787299 reported by Dan Kegel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This is on a fresh Dell 8930 with an i7-8700 (and a gtx1050) running ubuntu 18.04.
Linux rbb-ubu1804-1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Oddly this only happens on one of the two such boxes I have.

Here's the main warning I'm seeing:

Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113915] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113931] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113942] pcieport 0000:00:1c.2: device [8086:a292] error status/mask=00001000/00002000
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113950] pcieport 0000:00:1c.2: [12] Replay Timer Timeout

Happens kind of randomly; dmesg shows it happened 13 times in first 9 minutes;
syslog shows it happened 841 times in about 12 hours.

Also see a bit of this:

Aug 15 15:59:40 rbb-ubu1804-1 kernel: [ 385.278631] pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
Aug 15 15:59:40 rbb-ubu1804-1 kernel: [ 385.278635] pcieport 0000:00:1c.2: can't find device of ID00e2

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: buildbot 1881 F.... pulseaudio
 /dev/snd/controlC0: buildbot 1881 F.... pulseaudio
Date: Wed Aug 15 15:55:59 2018
HibernationDevice: RESUME=UUID=d0b594a3-6d1f-41af-bde1-89c3ec729d02
InstallationDate: Installed on 2018-08-14 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 8930
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.10
dmi.board.name: 0DF42J
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvr1.0.10:bd05/17/2018:svnDellInc.:pnXPS8930:pvr1.0.10:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.version: 1.0.10
dmi.sys.vendor: Dell Inc.

Revision history for this message
Dan Kegel (dank) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) 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 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.18 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.18

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.