nRF5340 device crash when we send DFU reset command (./mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='XXXX' reset)

Dear Nordic,

I'm developing a software with the nRF Connect SDK v2.4.1. This software runs Matter on the nRF5340.

During performing DFU(Based on SMP service),I need to reset the MCU from mobile app after transmitting the nordic image and confirm nordic image.

We are sending this command(sudo ./mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='XXXX' reset) to reset nordic device, 

this process working fine since last one year, but now I wanted to send feedback that nRF5340 has received reset command and wanted to send some message over BLE to moble app, so iI have enable the reset callback by using below config.

CONFIG_MCUMGR_GRP_OS_RESET_HOOK=y
CONFIG_MCUMGR_GRP_OS_RESET_MS=500
After that I am getting callback as well and inside that I am verifying the few things and sending BLE message to mobile app and after that nRF5340 device resettled.
But this makes the OS crash with the following trace. 
uart:~$ E: IPC endpoint bind timed out
ASSERTION FAIL @ WEST_TOPDIR/zephyr/drivers/ieee802154/ieee802154_nrf5.c:1244
E: r0/a1:  0x00000004  r1/a2:  0x000004dc  r2/a3:  0x2000e340
E: r3/a4:  0x200192a4 r12/ip:  0x00000000 r14/lr:  0x000354fb
E:  xpsr:  0x69100000
E: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
E: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000
E: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
E: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
E: fpscr:  0x000b81e0
E: Faulting instruction address (r15/pc): 0x00085e90
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x2000e340 (main)
E: Halting system
Is there any way to resolve this issue?
Related