PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018 (Transmitter ID)

My device gives this error everytime when I activate CAN Bus Line and I tried switching aspm from powersave mode to performance and default mode. This error still shows up. Can someone help me to solve the issue ? This error still comes into my log files and sometimes my device suddenly resets itself.

pcieport: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018 (Transmitter ID)
pcieport: device[someID] error status/mask=00001000/00002000
pcieport: [12] Replay Timer Timeout

pcan: PCAN-miniPCIe FD CAN1 Ctrlr Rx Buffer overrun (loss of frame?) IRQ380 count=114273

Hi gobildolma,

Are you using the devkit or custom board for TX2?
What’s the Jetpack version in use?

Please share the result of the following command on your board.

$ cat /etc/nv_boot_control.conf
$ cat /etc/nv_tegra_release

Could you share the steps how do you reproduce the issue? (i.e. how do you activate CAN bus?)
Are you connecting PCAN-PCIe module?

Hi Kevin, I am not using devkit. I have pcan card and video capture card in PCIe slot.

$ cat /etc/nv_boot_control.conf

TNSPEC 3310-D00-1000-M.0-1-0-cti/tx2/elroy-revF±mmcblk0p1
COMPATIBLE_SPEC 3310-B01—1–cti/tx2/elroy-revF±mmcblk0p1
TEGRA_CHIPID 0X18
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1

And for the line below

$ cat /etc/nv_tegra_release
R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t186ref, EABI: aarch64, DATE: Fri Oct 16 …

these are the outputs you requested. PCAN is connected with PCIe and another computer always sends data with the speed of 1000k. I can succesfully record my data but sometimes it just resets and doesn’t give any CAN data. I need to reset my tx2 to record data again. Even though it doesn’t reset itself this error still shows up in my syslogs.

pcan: PCAN-miniPCIe FD CAN1 Ctrlr Rx Buffer overrun (loss of frame?) IRQ380 count=114273

it says this one before resetting the device.

I use Peak system’s PCAN card.

Anyone have any idea ?

It is quite an old release. Could you simple update the devkit to the latest R32.7.5 to verify?

It seems like the error output from pcan driver.
Have you also asked your vendor for this error?

You can try just reload the driver instead of resetting the board to check if it can help.

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