Logging: Fault instruction address in the logging thread

[LingaoM]

Describe the bug
Every time power on, it will trigger the crash exception.

To Reproduce
Steps to reproduce the behavior:

1. mkdir build; cd build
2. west build -b nrf52840dk_nrf52840 zephyr/tests/bluetooth/mesh_shell/
3. west build -t menuconfig

Zephyr Kernel Version: 2.4.99

[00:00:17.732,574] bt_mesh_crypto.bt_mesh_beacon_auth: BeaconKey 001245a59b55cee65ede2ecd3706dba~
[00:00:17.732,574] bt_mesh_crypto.bt_mesh_beacon_auth: NetId c358e9488149e865
[00:00:17.732,574] bt_mesh_crypto.bt_mesh_beacon_auth: IV Index 0x00000000
[00:00:17.732,604] bt_mesh_crypto.bt_mesh_beacon_auth: BeaconMsg 00c358e9488149e86500000000
[00:00:17.733,123] bt_mesh_proxy.bt_mesh_proxy_adv_stop: adv_enabled 0
[00:00:17.734,802] bt_mesh_proxy.bt_mesh_proxy_gatt_enable:
[00:00:17.833,435] os: r0/a1: 0x00000004 r1/a2: 0x0000006d r2/a3: 0x200038d0
[00:00:17.833,465] os: r3/a4: 0x00000001 r12/ip: 0x00000000 r14/lr: 0x00004e8b
[00:00:17.833,465] os: xpsr: 0x61000000
[00:00:17.833,496] os: Faulting instruction address (r15/pc): 0x0002ef4c
[00:00:17.833,496] os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:17.833,526] os: Current thread: 0x20000e08 (logging)
[00:00:18.510,375] os: Halting system

$: ~/zephyr-sdk-0.11.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-addr2line -e zephyr/zephyr.elf -a 0x00004e8b
0x00004e8b
/home/lingao/zephyrproject/zephyr/subsys/shell/shell_log_backend.c:190

[LingaoM]

autoconf.zip

[ioannisg]

@trond-snekvik maybe you could take a look at this mesh-related test issue?

[trond-snekvik]

@ioannisg This error is happening on the logging thread, I can't quite see how the mesh shell module is interfering.
Deferring to shell module code owners, but I'll stick around in case there's something wrong in the mesh usage of shell.

[carlescufi]

/home/lingao/zephyrproject/zephyr/subsys/shell/shell_log_backend.c:190:

zephyr/subsys/shell/shell_log_backend.c

Line 190 in 889e37b

signal = &shell->ctx->signals[SHELL_SIGNAL_LOG_MSG];

@LingaoM is this the same line you see on your local copy?

[nordic-krch]

@LingaoM can you attach prj.conf file that was used. It is hard to compare autoconf.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.