This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VH-Q1: TDA4VH sdk8.6 kernel crash issue

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Hi Ti, expert

        sdk version: 08_06_00_12

        BOARD:      tda4vh custome board

        BOOT mode:  SBL

        On TDA4VH, there is an error that occurs once every 2-3 days:

[2023-10-10 10:20:24] [   51.963925] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: hrtimer_nanosleep+0x118/0x118
[2023-10-10 10:20:24] [   51.974443] CPU: 0 PID: 721 Comm: mcumsg_client Tainted: G           O      5.10.162-g76b3e88d56 #1
[2023-10-10 10:20:24] [   51.983471] Hardware name: HIKAUTO AE-B50036-M (DT)
[2023-10-10 10:20:24] [   51.988341] Call trace:
[2023-10-10 10:20:24] [   51.990793]  dump_backtrace+0x0/0x1a0
[2023-10-10 10:20:25] [   51.994449]  show_stack+0x18/0x28
[2023-10-10 10:20:25] [   51.997758]  dump_stack+0xc8/0x120
[2023-10-10 10:20:25] [   52.001151]  panic+0x16c/0x340
[2023-10-10 10:20:25] [   52.004196]  __stack_chk_fail+0x30/0x40
[2023-10-10 10:20:25] [   52.008025]  __arm64_sys_nanosleep+0x0/0xd0
[2023-10-10 10:20:25] [   52.012197]  __arm64_sys_nanosleep+0x94/0xd0
[2023-10-10 10:20:25] [   52.016456]  el0_svc_common.constprop.0+0x80/0x260
[2023-10-10 10:20:25] [   52.021231]  do_el0_svc+0x24/0x90
[2023-10-10 10:20:25] [   52.024535]  el0_svc+0x14/0x20
[2023-10-10 10:20:25] [   52.027576]  el0_sync_handler+0xb0/0xb8
[2023-10-10 10:20:25] [   52.031397]  el0_sync+0x180/0x1c0
[2023-10-10 10:20:25] [   52.034705] SMP: stopping secondary CPUs
[2023-10-10 10:20:25] [   52.038622] Kernel Offset: disabled
[2023-10-10 10:20:25] [   52.042097] CPU features: 0x28040422,20006008
[2023-10-10 10:20:25] [   52.046438] Memory Limit: none
[2023-10-10 10:20:25] [   52.049483] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: hrtimer_nanosleep+0x118/0x118 ]---

     We have checked the mpu of R5 and mmu of c71 to ensure that rtos do not affect Linux. 

     Could TI experts please help identify the possible causes of this issue? Thank you very much.

Best Regards,

Alex