You are not logged in.

#1 2017-04-25 12:52:56

conan1989
Member
Registered: 2014-12-22
Posts: 6

Am i debugging this right? "PCIe Bus Error"

Hi,
I'm having some issues with my system, keeps crashing (keyboard, mouse, and monitor freeze. Audio continues to play just fine)
If someone is able to confirm my method for figuring this out is right, thanks.


Kernel: 4.10.11-1
NVMe: Intel 750 SSD (400GB)
CPU: Intel i7 6850K


I think something is bad with either / both
"00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01)"
"02:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01)"


error

[conan@grunt ~]$ journalctl -xe
Apr 25 22:10:49 grunt plasmashell[788]: notification inhibited. Skipping
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP
Apr 25 22:10:50 grunt NetworkManager[548]: <info>  [1493122250.8888] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 25 22:10:50 grunt nm-dispatcher[1065]: req:2 'connectivity-change': new request (0 scripts)
Apr 25 22:10:50 grunt nm-dispatcher[1065]: req:2 'connectivity-change': completed: no scripts
Apr 25 22:10:51 grunt kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Apr 25 22:10:51 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Apr 25 22:10:51 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Apr 25 22:10:51 grunt kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP
Apr 25 22:10:52 grunt kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Apr 25 22:10:52 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Apr 25 22:10:52 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Apr 25 22:10:52 grunt kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP
Apr 25 22:10:52 grunt kdeconnectd[786]: kdeconnect.core: Broadcasting identity packet
Apr 25 22:10:53 grunt kernel: pcieport 0000:00:03.0: AER: Corrected error received: id=0018
Apr 25 22:10:53 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID)
Apr 25 22:10:53 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00001000/00002000
Apr 25 22:10:53 grunt kernel: pcieport 0000:00:03.0:    [12] Replay Timer Timeout
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0008
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0008(Receiver ID)
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:01.0:   device [8086:6f02] error status/mask=00000040/00002000
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:01.0:    [ 6] Bad TLP
Apr 25 22:10:54 grunt kernel: pcieport 0000:00:01.0:   Error of this Agent(0008) is reported first
Apr 25 22:10:54 grunt kernel: nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0200(Receiver ID)
Apr 25 22:10:54 grunt kernel: nvme 0000:02:00.0:   device [8086:0953] error status/mask=00000001/00002000
Apr 25 22:10:54 grunt kernel: nvme 0000:02:00.0:    [ 0] Receiver Error         (First)

lspci

00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01)
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)
00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)
00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01)
00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01)
00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01)
00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01)
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05)
00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05)
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 (rev d5)
00:1c.6 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #7 (rev d5)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GM200 [GeForce GTX TITAN X] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GM200 High Definition Audio (rev a1)
02:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 01)
05:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03)
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
07:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
ff:0b.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
ff:0b.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
ff:0b.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
ff:0b.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug (rev 01)
ff:0c.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0c.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0c.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0c.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0c.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0c.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0f.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0f.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0f.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:0f.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
ff:10.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01)
ff:10.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01)
ff:10.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
ff:10.6 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
ff:10.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
ff:12.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01)
ff:12.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01)
ff:13.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01)
ff:13.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01)
ff:13.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
ff:13.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
ff:13.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
ff:13.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
ff:13.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast (rev 01)
ff:13.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01)
ff:14.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control (rev 01)
ff:14.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control (rev 01)
ff:14.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error (rev 01)
ff:14.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error (rev 01)
ff:14.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
ff:14.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
ff:14.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
ff:14.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
ff:15.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control (rev 01)
ff:15.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control (rev 01)
ff:15.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error (rev 01)
ff:15.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error (rev 01)
ff:16.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS (rev 01)
ff:16.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast (rev 01)
ff:16.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01)
ff:17.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control (rev 01)
ff:17.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
ff:17.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
ff:17.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
ff:17.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
ff:1e.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1e.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1e.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1e.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1e.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
ff:1f.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[conan@grunt ~]$ dmesg | grep microcode
[    0.000000] microcode: microcode updated early to revision 0xb00001f, date = 2016-10-07
[    9.737860] microcode: sig=0x406f1, pf=0x4, revision=0xb00001f
[    9.737977] microcode: Microcode Update Driver: v2.2.

Last edited by conan1989 (2017-04-25 12:59:47)

Offline

#2 2017-04-25 12:56:34

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: Am i debugging this right? "PCIe Bus Error"

Please edit your post and use [ code ] tags around the terminal output.

https://bbs.archlinux.org/help.php#bbcode

Last edited by 2ManyDogs (2017-04-25 12:57:47)

Offline

#3 2017-04-25 13:00:01

conan1989
Member
Registered: 2014-12-22
Posts: 6

Re: Am i debugging this right? "PCIe Bus Error"

done. thanks

Offline

#4 2017-04-25 13:09:12

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: Am i debugging this right? "PCIe Bus Error"

Have you tried searching for some of those error messages? I did and get hits on topics suggesting updating the NVMe firmware or booting with different kernel parameters. I don't know enough about your specific hardware to know if those are reasonable suggestions.

Have you tried a different kernel? You could try the LTS kernel (linux-lts) just to see if the problem is kernel related.

Offline

#5 2017-04-25 13:38:41

blahhumbug
Member
Registered: 2016-10-08
Posts: 64

Re: Am i debugging this right? "PCIe Bus Error"

PCIe, being a high speed bus, is actually designed to tolerate some amount of bit-errors.   The specific errors you are getting in the log are considered Correctable errors that should not make the system unusable.

 
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)

When a Bad TLP error occurs the detecting root-port does not ACK the packet, and the attached PCIe card will resend the packet.  The final error is a 'Receiver Error' and this type of error does usually mean that the PCIe link needs to retrain itself.   If somehow it is failing to retrain, that would mean the attached NVMe disk is now unreachable.   .

However, if the link is failing to retrain, the root-port should be logging a Surprise Link Down error which is an Uncorrectable error,  Generally, if the log only has PCIe correctable errors, these should not be fatal to the system and might be a red-herring.   But if you are seeing these errors everytime right as the system hangs, and if the NVMe disk is your boot disk, then there probably is a relation.

I'd recommend keeping your eye on the log and see if these errors ever show up without a system-hang occurring.  You might also want to power down and re-seat the NVMe card.  If system stability problems continues, many BIOS implementations let you force the PCIe links to train to gen2 speeds instead of gen3 speeds.  The link may become more reliable at a slower clock speed, although you'd lose about half your bandwidth.  Alternatively, if you have a different unused slot on your motherboard, I would try moving your NVMe disk to that slot.

Last edited by blahhumbug (2017-04-25 13:49:46)

Offline

#6 2017-04-27 11:59:31

conan1989
Member
Registered: 2014-12-22
Posts: 6

Re: Am i debugging this right? "PCIe Bus Error"

2ManyDogs wrote:

Have you tried searching for some of those error messages? I did and get hits on topics suggesting updating the NVMe firmware or booting with different kernel parameters. I don't know enough about your specific hardware to know if those are reasonable suggestions.

Have you tried a different kernel? You could try the LTS kernel (linux-lts) just to see if the problem is kernel related.



yep.
Bunch of web searches, and specific web site searches (reddit subs, few of the common forums (including this one))
Few said how to suppress the errors, a bunch of troubleshooting 101 questions. No good answers

Motherboard and SSD firmware are up to date as of a week ago. Issues persisted.

A weird one though. went to linux-lts and nvidia-lts, issues remain. Went back to normal linux and nvidia, no issues since.
I can't make sense of that. You?

now that i've written this, it'll probably trip again though haha.

boot parameters are the same

[conan@grunt ~]$ dmesg | grep "Command line"
[    0.000000] Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=PARTUUID=9b7aea38-a162-4f62-a9dd-7000a4000a26

and thank you by the way. Really!

Offline

#7 2017-04-27 12:05:40

conan1989
Member
Registered: 2014-12-22
Posts: 6

Re: Am i debugging this right? "PCIe Bus Error"

blahhumbug wrote:

PCIe, being a high speed bus, is actually designed to tolerate some amount of bit-errors.   The specific errors you are getting in the log are considered Correctable errors that should not make the system unusable.

 
Apr 25 22:10:50 grunt kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)

When a Bad TLP error occurs the detecting root-port does not ACK the packet, and the attached PCIe card will resend the packet.  The final error is a 'Receiver Error' and this type of error does usually mean that the PCIe link needs to retrain itself.   If somehow it is failing to retrain, that would mean the attached NVMe disk is now unreachable.   .

However, if the link is failing to retrain, the root-port should be logging a Surprise Link Down error which is an Uncorrectable error,  Generally, if the log only has PCIe correctable errors, these should not be fatal to the system and might be a red-herring.   But if you are seeing these errors everytime right as the system hangs, and if the NVMe disk is your boot disk, then there probably is a relation.

I'd recommend keeping your eye on the log and see if these errors ever show up without a system-hang occurring.  You might also want to power down and re-seat the NVMe card.  If system stability problems continues, many BIOS implementations let you force the PCIe links to train to gen2 speeds instead of gen3 speeds.  The link may become more reliable at a slower clock speed, although you'd lose about half your bandwidth.  Alternatively, if you have a different unused slot on your motherboard, I would try moving your NVMe disk to that slot.



Thank you! Just learned something about PCI!

Think you're right about the red herring.
Still getting the errors, but not having the crashes since going to the LTS version and back again.
Not sure what to make of that though

Can't see anything interesting in the logs. Unless i'm looking in the wrong logs / not recognising something

Offline

Board footer

Powered by FluxBB