Pcieport 0004:00:00.0: AER: can't find device of ID0000

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

Hi
I’m using a custom Orin NX board and it occasionally reports ‘PCIe AER: can’t find device of ID0000’ during reboot testing, and it requires a reboot to recover. We also find the message ‘pcie_tegra194: module verification failed: signature and/or required key missing - tainting kernel,’ but this message can also be seen on devices that boot normally. What could possibly be causing this issue?

[    9.444831] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000020/00400000
[    9.444834] pcieport 0004:00:00.0:    [ 5] SDES                   (First)
[    9.445143] tegra194-pcie 141e0000.pcie: iATU unroll: enabled
[    9.445148] tegra194-pcie 141e0000.pcie: Detected iATU regions: 8 outbound, 2 inbound
[    9.453013] pcieport 0004:00:00.0: AER: Root Port link has been reset (0)
[    9.453024] pcieport 0004:00:00.0: AER: device recovery successful
[    9.485470] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.485486] pcieport 0004:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    9.485489] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000001/0000e000
[    9.485492] pcieport 0004:00:00.0:    [ 0] RxErr                  (First)
** 893 printk messages dropped **
[    9.513448] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 1225 printk messages dropped **
[    9.521879] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 4 printk messages dropped **
[    9.521910] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000001/0000e000
** 1 printk messages dropped **
[    9.522007] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 10 printk messages dropped **
[    9.522476] pcieport 0004:00:00.0:    [ 0] RxErr                  (First)
** 4 printk messages dropped **
[    9.522576] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000001/0000e000
** 4 printk messages dropped **
[    9.522594] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 1 printk messages dropped **
[    9.522599] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.522600] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.522604] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 85 printk messages dropped **
[    9.522843] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 46 printk messages dropped **
[    9.523489] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 1 printk messages dropped **
[    9.523545] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000001/0000e000
[    9.523586] pcieport 0004:00:00.0:    [ 0] RxErr                  (First)
[    9.523609] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523616] pcieport 0004:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[    9.523625] pcieport 0004:00:00.0:   device [10de:229c] error status/mask=00000001/0000e000
[    9.523626] pcieport 0004:00:00.0:    [ 0] RxErr                  (First)
[    9.523633] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523637] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523638] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523643] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523643] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523648] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523649] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523653] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523654] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523658] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523659] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523664] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523665] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523670] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523671] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.523675] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523676] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 18 printk messages dropped **
[    9.523729] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.523729] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 5 printk messages dropped **
[    9.523745] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 424 printk messages dropped **
[    9.526831] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 399 printk messages dropped **
[    9.529167] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 361 printk messages dropped **
[    9.532086] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 3 printk messages dropped **
[    9.532098] pcieport 0004:00:00.0: AER: can't find device of ID0000
** 1 printk messages dropped **
[    9.532103] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.532104] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
[    9.532109] pcieport 0004:00:00.0: AER: can't find device of ID0000
[    9.532109] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 7 printk messages dropped **
[    9.532131] pcieport 0004:00:00.0: AER: Multiple Corrected error received: 0004:00:00.0
** 6 printk messages dropped **

Thanks

3

It could be hardware issue if same pcie device can work fine on NV devkit.

4

Sure, thanks for your reply

5

Hello, may I ask if the hardware issue you mentioned can be specifically pointed to a particular hardware PCIe channel? Could you also provide the troubleshooting direction?

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.