pcieport 0000:00:1b.4: PCIe Bus Error...

ZioMario

ZioMario

Hello.

Hi, I have a recurring error that I have noticed in the logs of Ubuntu 24.04 that I can't track down ! But it seems that all my PCIe cards seem to function correctly,infact at the moment I'm using FreeBSD and I don't see that error when I issue the command "dmesg -a".

Code: 
[  408.981747] pcieport 0000:00:1b.4: PCIe Bus Error:  severity=Correctable, type=Physical Layer, (Receiver ID)
[  408.981748] pcieport 0000:00:1b.4:   device [8086:a32c] error status/mask=00000001/00002000
[  408.981749] pcieport 0000:00:1b.4:    [ 0] RxErr                 (First)
[  408.981757] pcieport 0000:00:1b.4: AER: Correctable error message received from 0000:00:1b.4
[  408.981767] pcieport 0000:00:1b.4: AER: found no error details for 0000:00:1b.4

It seems the same bug reported here :

https://forums.unraid.net/topic/82644-pcie-error/

but I'm not using UnRaid. Is there a specific place where FreeBSD can print this error ? I want to understand if the error is related to Ubuntu 24.04 or if it is an hardware fault.
 
ZioMario said:
I want to understand if the error is related to Ubuntu 24.04 or if it is an hardware fault.
Click to expand...
How about neither? PCIe has been designed to be resilient and somewhat forgiving with regard to bus errors. It's been corrected at the hardware level. Linux has a thing called AER that simply triggers on those errors and bombards you with useless, scary looking, messages. Just turn it off.
 
Good advice,I'm reading that could be disabled with :

Code: 
pcie_aspm=off

but it's not sure that it works. Anyway,just trying...
 
I've seen ARI Correctable errors like that with my NVMe when enabling IOMMU, but only sometimes. The first things I'd mess around with in BIOS are IOMMU and above 4G decode.
 
My motherboard does not support IOMMU. It has the option called "4G decode",but I'm scared to modify it. I did it some years ago and I saw some malfunctions. Instead,I've added the parameter "pcie_aspm=off" to the kernel of one of my two Linux installations and the error is disappeared for one of them,but it did not for the second one. Maybe the version of the kernel also matter.
 
You must log in or register to reply here.
Back
Top