RPMSG SDB driver failure on M4 restart

[mishuk]

Recently I got a problem with RPMSG driver when M5 coprocessor restarts. Thanks to https://community.st.com/s/question/0D53W00000936uRSAQ/kernel-panic-with-pollselect-syscalls-on-virtual-uart-devices-to-m4-core-when-m4-watchdog-restarts?t=1632144260162

the problem is over.

Now I get the same problem with RPMSG SDB driver (see attachment). Can you help me ?

[SergeyBlagodarnyy]

I have the same problem.

I wrote an echo test which sends the request with rpmsg from A7 to M4. M4 replies using sdb. When I restart the M4, whith A7 working, I have a kernel internal error.

Do anyone had with this problem?

skrm:~/utc/v# ./start_firmware.sh mt_sdb.elf
skrm:~/utc/v# ./stop_firmware.sh 
skrm:~/utc/v# 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.278142] Internal error: Oops: 7 [#1] PREEMPT SMP ARM
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.361428] Process sdb_manual_test (pid: 2129, stack limit = 0x75efe24f)
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.368207] Stack: (0xccf11db0 to 0xccf12000)
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.372560] 1da0:                                     d12efb80 d12efba4 00000000 c0946f6c
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.380739] 1dc0: d12efbec c1204e88 d12efb80 d12efb80 d12efbec c0947670 ccf11e7c ccf11dfc
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.388917] 1de0: c0e3d194 c0bfeba4 00000400 00000000 ccf11e5c ccccc600 00000000 ccdba1c0
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.397093] 1e00: c0168e44 d12efbe4 d12efbe4 c1204e88 ccdb631c 00000014 ccdb631c bf082300
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.405267] 1e20: 000001f0 00000000 ccf11e5c ccccc600 00000000 c09478a8 00000014 00000001
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.413445] 1e40: bf081148 bf0803fc d20d0000 00008000 ccf11e60 c02bb63c ccf10000 64413042
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.421618] 1e60: 30643032 4c303030 30303030 30303038 ccd73400 cce4df10 ccd73400 c1204e88
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.429795] 1e80: cce18cc0 cce4df10 cce4df18 b6f78000 cce18cc0 00000000 ccd2eb40 00000008
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.437974] 1ea0: ccd73400 c028d78c 00100073 00000000 ccdcea80 00000000 00000000 00002000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.446149] 1ec0: 00100073 ccdcea80 00000008 00000000 ccdce841 00008000 c0118ff0 00008000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.454327] 1ee0: 00000002 00000073 ccdcea80 b6f78000 00000003 00000008 ccd73400 c028dd8c
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.462504] 1f00: 00000000 ccf11f54 beea1e54 00000073 ccf10000 ccd73440 ccdcea80 00000000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.470677] 1f20: 00008000 00000003 ccf11f54 000000c0 00000000 c026e2d4 00000002 00000000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.478854] 1f40: 00000000 ccf11f50 ccf11f54 0000000a 00000000 ccf11f54 ccf11f54 c1204e88
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.487028] 1f60: 000000c0 00000002 00000003 00008000 00000000 00000000 ccdcea80 c028b670
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.495204] 1f80: 00000002 00000000 00000000 0000000a 00000000 00008000 000000c0 c0101204
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.503381] 1fa0: ccf10000 c0101000 0000000a 00000000 00000000 00008000 00000003 00000002
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.511555] 1fc0: 0000000a 00000000 00008000 000000c0 000a6d68 00000000 41029fa4 00000000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.519732] 1fe0: 000000c0 beea1e24 410c8be7 4104c026 40030030 00000000 00000000 00000000
 
 
Broadcast message from systemd-journald@skrm (Fri 2020-02-07 16:01:36 UTC):
 
kernel[889]: [  652.630449] Code: e3530000 1afffffb e5901040 e1d003b0 (e1d110b2)

[SMich.1]

I have something similar after I updated my project Yocto to Kirkstone the sdb driver is crushing when I stop my processes with kill -9 with sigterm no matter how sometimes crushing because it some wrong address referencing to 0x000000 sometimes another errors. Is some one from ST can help us?