BadDLLP PCIE Port

NYSundevil

Dabbler
Joined
Nov 22, 2020
Messages
13
My server continually generates these PCIe Errors, everything seems to work but I'd like to understand the issue and resolve it before installing more app. I currently only run Plex and have 1 Windows VM that is usually stopped, haven't figured out how to pass through SMB share yet.
My hardware is ASUS Prime Z490M-Plus MB with i5-10600 CPU. The issue started when I populated both PCIe x16 slots. I replaced my sata expansion card that used PCIe x1 slot with a 9207-8I from eBay. The other PCIe 16 slot holds an Intel X550-T2 clone I got off Amazon. I get no errors when either card is removed. Other relevant hardware is I have two Inland 512GB SSDs in the M.2 slots. I've tried to change Bios settings related to PCIe but no dice. Any help is appreciated.


Jul 17 21:39:11 truenas kernel: pcieport 0000:00:1b.3: device [8086:06c3] error status/mask=00001080/00002000
Jul 17 21:39:11 truenas kernel: pcieport 0000:00:1b.3: [ 7] BadDLLP
Jul 17 21:39:11 truenas kernel: pcieport 0000:00:1b.3: [12] Timeout
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: device [8086:06c3] error status/mask=00000001/00002000
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: [ 0] RxErr
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:15 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: can't find device of ID00db
Jul 17 21:39:16 truenas kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
According to the manual for this motherboard, it supports CrossFireX for GPU pairing. Is it possible to disable CrossFireX in the BIOS? Neither the HBA nor the NIC appear to understand CrossFireX. Try moving them to x8 or x4 slots.
 
Last edited:

NYSundevil

Dabbler
Joined
Nov 22, 2020
Messages
13
Thank you!
I will take a look at the CrossFireX setting in the BIOS. Both cards require the longer slots and the board only has 2 longer slots so I don't have any other options.
 

NYSundevil

Dabbler
Joined
Nov 22, 2020
Messages
13
There are no Crossfire settings in the BIOS. I tried changing a few more settings but am still getting the same errors. Including disabling ASPM but same exact errors. Is there a boot command I can add to suppress them or prevent checking?Looks like other Linux OS suggest adding lines to the grub file
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
Does this make sense? If so how would I go about doing this in Scale?
 
Top