Jp5.1.1 orin nx system restart abnormally

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

Our customized board often restarted abnormally at the customer’s factories. Please help to analyze.The log is attacted.The following mistakes occur a lot. What are the reasons? Can it affect other functions?
log.txt (562.4 KB)

[ 1215.714545] Call trace:
[ 1215.717058] tegra186_gpio_irq+0x1ac/0x1f0
[ 1215.721245] generic_handle_irq+0x40/0x60
[ 1215.725348] __handle_domain_irq+0x70/0xd0
[ 1215.729537] gic_handle_irq+0x68/0x134
[ 1215.733375] el1_irq+0xd0/0x180
[ 1215.736592] __do_softirq+0xb4/0x3e8
[ 1215.740250] irq_exit+0xc0/0xe0
[ 1215.743462] __handle_domain_irq+0x74/0xd0
[ 1215.747650] gic_handle_irq+0x68/0x134
[ 1215.751488] el1_irq+0xd0/0x180
[ 1215.754700] cpuidle_enter_state+0xb8/0x410
[ 1215.758985] cpuidle_enter+0x40/0x60
[ 1215.762639] call_cpuidle+0x44/0x80
[ 1215.766209] do_idle+0x208/0x270
[ 1215.769513] cpu_startup_entry+0x2c/0x70
[ 1215.773536] rest_init+0xdc/0xe8
[ 1215.776840] arch_call_rest_init+0x18/0x20
[ 1215.781034] start_kernel+0x514/0x54c
[ 1215.784775] —[ end trace e80567ec1ffced3b ]—
[ 1215.789535] ------------[ cut here ]------------
[ 1215.794264] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0

3

This is a known issue on Jetpack5 and won’t be fixed. Please move to Jetpack6.

4

But why did it restart? Is it because of the tegra186_gpio error? Will this error cause a reboot?Is it okay to upgrade to JP5.1.5 to solve this problem?

5

No, this is a known issue and won’t be fixed in Jetpack5. Only Jetpack6 has the fix.

6

As we know this error will not cause a restart, I just need to solve the restart problem.I don’t care tegra186_gpio error.

7

tegra186_gpio will cause restart if ghost interrupt didn’t get clear by any driver.

8

So now the customer has gotten this problem,is there any way to help me clear the interruption? It’s very urgent.Or is the only way to burn it again? How can customers avoid this problem? Upgrading to the Jetpack6 need to take a long time.

9

There is only one workaround to avoid this issue.

do this before powerdown/reboot/suspend to avoid problem.

1 Like