Patch for AGX Xavier freeze in MAXN mode

I often experience a sudden shutdown of AGX Xavier with kernel message like below and it looks similar to the message reported in the existing thread:

I found that a patch for kernel is proposed in another thread:

In the thread, the patch is being merged to mainline, is the patch already merged to L4T?
If true, from which version is the patch applied to?

@WayneWWW

6月 16 10:20:08 r1 kernel: INFO: rcu_preempt self-detected stall on CPU
 6月 16 10:20:08 r1 kernel:     4-...: (1 GPs behind) idle=433/2/0 softirq=9440/9441 fqs=2454 
 6月 16 10:20:08 r1 kernel:      (t=5250 jiffies g=2637 c=2636 q=203776)
 6月 16 10:20:08 r1 kernel: Task dump for CPU 4:
 6月 16 10:20:08 r1 kernel: swapper/4       R  running task        0     0      1 0x00000002
 6月 16 10:20:08 r1 kernel: Call trace:
 6月 16 10:20:08 r1 kernel: [<ffffff800808ba40>] dump_backtrace+0x0/0x198
 6月 16 10:20:08 r1 kernel: [<ffffff800808c004>] show_stack+0x24/0x30
 6月 16 10:20:08 r1 kernel: [<ffffff80080ec278>] sched_show_task+0xf8/0x148
 6月 16 10:20:08 r1 kernel: [<ffffff80080ef000>] dump_cpu_task+0x48/0x58
 6月 16 10:20:08 r1 kernel: [<ffffff8008f5e954>] rcu_dump_cpu_stacks+0xb8/0xec
 6月 16 10:20:08 r1 kernel: [<ffffff8008131980>] rcu_check_callbacks+0x728/0xa48
 6月 16 10:20:08 r1 kernel: [<ffffff80081381dc>] update_process_times+0x34/0x60
 6月 16 10:20:08 r1 kernel: [<ffffff8008149700>] tick_sched_handle.isra.5+0x38/0x70
 6月 16 10:20:08 r1 kernel: [<ffffff8008149784>] tick_sched_timer+0x4c/0x90
 6月 16 10:20:08 r1 kernel: [<ffffff8008138f10>] __hrtimer_run_queues+0xd8/0x360
 6月 16 10:20:08 r1 kernel: [<ffffff8008139860>] hrtimer_interrupt+0xa8/0x1e0
 6月 16 10:20:08 r1 kernel: [<ffffff8008bfab20>] arch_timer_handler_phys+0x38/0x58
 6月 16 10:20:08 r1 kernel: [<ffffff8008126410>] handle_percpu_devid_irq+0x90/0x2b0                           "r1" 10:20 16- 6月-22
 6月 16 10:20:08 r1 kernel: [<ffffff80081208f4>] generic_handle_irq+0x34/0x50
 6月 16 10:20:08 r1 kernel: [<ffffff8008120fe0>] __handle_domain_irq+0x68/0xc0
 6月 16 10:20:08 r1 kernel: [<ffffff8008080d44>] gic_handle_irq+0x5c/0xb0
 6月 16 10:20:08 r1 kernel: [<ffffff8008082c28>] el1_irq+0xe8/0x194
 6月 16 10:20:08 r1 kernel: [<ffffff80080ba090>] irq_exit+0xd0/0x118
 6月 16 10:20:08 r1 kernel: [<ffffff8008120fe4>] __handle_domain_irq+0x6c/0xc0
 6月 16 10:20:08 r1 kernel: [<ffffff8008080d44>] gic_handle_irq+0x5c/0xb0
 6月 16 10:20:08 r1 kernel: [<ffffff8008082c28>] el1_irq+0xe8/0x194
 6月 16 10:20:08 r1 kernel: [<ffffff8008ba09e0>] cpuidle_enter_state+0xb8/0x380
 6月 16 10:20:08 r1 kernel: [<ffffff8008ba0d1c>] cpuidle_enter+0x34/0x48
 6月 16 10:20:08 r1 kernel: [<ffffff800811139c>] call_cpuidle+0x44/0x70
 6月 16 10:20:08 r1 kernel: [<ffffff8008111718>] cpu_startup_entry+0x1b0/0x200
 6月 16 10:20:08 r1 kernel: [<ffffff8008091cf8>] secondary_start_kernel+0x190/0x1f8
 6月 16 10:20:08 r1 kernel: [<0000000080f6e1a8>] 0x80f6e1a8
 6月 16 10:20:08 r1 kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
 6月 16 10:20:08 r1 kernel:     4-...: (1 GPs behind) idle=433/2/0 softirq=9438/9441 fqs=2475 
 6月 16 10:20:08 r1 kernel:     (detected by 2, t=5252 jiffies, g=814, c=813, q=7557)
 6月 16 10:20:08 r1 kernel: Task dump for CPU 4:
 6月 16 10:20:08 r1 kernel: swapper/4       R  running task        0     0      1 0x00000002
 6月 16 10:20:08 r1 kernel: Call trace:
 6月 16 10:20:08 r1 kernel: [<ffffff800808604c>] __switch_to+0x9c/0xc0
 6月 16 10:20:08 r1 kernel: [<ffffff8008ba09c8>] cpuidle_enter_state+0xa0/0x380
 6月 16 10:20:08 r1 kernel: [<ffffff8008ba0d1c>] cpuidle_enter+0x34/0x48
 6月 16 10:20:08 r1 kernel: [<ffffff800811139c>] call_cpuidle+0x44/0x70
 6月 16 10:20:08 r1 kernel: [<ffffff8008111718>] cpu_startup_entry+0x1b0/0x200
 6月 16 10:20:08 r1 kernel: [<ffffff8008091cf8>] secondary_start_kernel+0x190/0x1f8
 6月 16 10:20:08 r1 kernel: [<0000000080f6e1a8>] 0x80f6e1a8
 6月 16 10:20:08 r1 env[8756]: status is sent
lines 613-692/692 (END)

Try rel-32.7.2.

@WayneWWW Thank you for the reply! I’m trying and waiting for an answer for another issue Sdkmanager 1.8.0 GUI not showing up on ubuntu 18.04

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