Orin system sometimes will stuck

I use AGX Orin 64GB with jetpack version is 5.1.2 and Linux kernel version is L4T 35.3.1.
I found my system sometimes will stuck about 400ms. When it happened, no can message:

v4l2 polling will timeout.
“eth1” networking card will not notify received message.
But application logs still print, so CPU may stil alive.
And syslog has no error report.
96a8766c-866a-4fc6-b49d-417959d948ac (1).log (59.9 KB)
So any suggestion to trace this problem?

Hi ckt10101,

L4T R35.3.1 should be included in JP5.1.1.
Please share the result of the following command.

$ cat /etc/nv_tegra_release

Are you using the devkit or custom board for AGX Orin?

How do you know about 400ms?

May I know what’s your use case and how do you reproduce this issue?

cat /etc/nv_tegra_release
# R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug  1 19:57:35 UTC 2023

I use custom board as I told on other thread.

How do you know about 400ms?

I count camera, can bus and lidar lost frame.

May I know what’s your use case and how do you reproduce this issue?

It happened when robot on automatic driving, and I don’t know how to reproduce.

We would need the detailed reproduce steps to verify on the devkit to perform further debug.

It seems you are using the custom board, then I want to know if the devkit has the same issue.

For the error message from mttcan, may I know what’s the bitrate you used for CAN?

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