Kexec sm_queue_stdcall busy issue

Every so often when I use kexec on the Xavier NX it will give the following message and halt the boot of the new OS:

[  153.135803] [TRUSTY] sm_queue_stdcall: cpu 2, std call busy

I noticed that this happens before the kernel constantly prints the std call buy message:

[   15.276161] trusty crashed[   15.276175] trusty trusty: nop_work_func: SMC_SC_NOP failed -11
[   15.276238] trusty trusty: nop_work_func: SMC_SC_NOP failed -11
[   15.277153] ------------[ cut here ]------------
[   15.281816] WARNING: CPU: 1 PID: 1 at /build/connecttech005-kernel-src/kernel/nvidia/drivers/trusty/trusty.c:264 trusty_std_call32+0x238/0x248
[   15.294141] Modules linked in:
[   15.297042]
[   15.298631] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W       4.9.140-tegra #1
[   15.306479] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[   15.312867] task: ffffffc1f6b28000 task.stack: ffffffc1f6b24000
[   15.318731] PC is at trusty_std_call32+0x238/0x248
[   15.323465] LR is at trusty_std_call32+0x238/0x248
[   15.328532] pc : [<ffffff8008cb2900>] lr : [<ffffff8008cb2900>] pstate: 40c00045
[   15.335798] sp : ffffffc1f6b27ab0
[   15.339123] x29: ffffffc1f6b27ac0 x28: 00000000fffffff5
[   15.345067] x27: 0000000000000018 x26: ffffffc1f5fb7e00
[   15.350754] x25: ffffffc1e4a6a000 x24: 0000000000000000
[   15.356528] x23: 0000000000000000 x22: 0000000000000000
[   15.362056] x21: 0000000000000000 x20: 0000000032000017
[   15.367656] x19: ffffffc1f5a79c10 x18: 0000000000000000
[   15.373591] x17: 000000000000001a x16: 000000000026be00
[   15.379278] x15: 0000000000000010 x14: ffffffffffffffff
[   15.384966] x13: ffffff808a176bf2 x12: ffffff800a176bfa
[   15.390319] x11: 0000000000000007 x10: 00000000000002c5
[   15.395920] x9 : 00000000ffffffd0 x8 : ffffff80083cbfa0
[   15.401942] x7 : ffffff8009f378d0 x6 : ffffff80083cb410
[   15.407206] x5 : 0000000000000000 x4 : 0000000000000000
[   15.412791] x3 : ffffffffffffffff x2 : ffffff8009f07a08
[   15.417883] x1 : ffffffc1f6b28000 x0 : 000000000000000e
[   15.423219]
[   15.424610] ---[ end trace 31bb15e2d8e212f3 ]---
[   15.429073] Call trace:
[   15.431789] [<ffffff8008cb2900>] trusty_std_call32+0x238/0x248
[   15.437210] [<ffffff8008cb4e40>] trusty_virtio_reset+0x50/0x80
[   15.442553] [<ffffff80086b304c>] register_virtio_device+0x84/0x110
[   15.448327] [<ffffff8008cb59b4>] trusty_virtio_add_devices+0x23c/0x578
[   15.454450] [<ffffff8008cb5dfc>] trusty_virtio_probe+0x10c/0x1b8
[   15.460311] [<ffffff800876daa0>] platform_drv_probe+0x60/0xc0
[   15.465648] [<ffffff800876b020>] really_probe+0xb0/0x358
[   15.470721] [<ffffff800876b40c>] driver_probe_device+0x4c/0xc8
[   15.476064] [<ffffff800876b580>] __driver_attach+0xf8/0x120
[   15.481661] [<ffffff8008768c70>] bus_for_each_dev+0x78/0xb8
[   15.486909] [<ffffff800876a920>] driver_attach+0x30/0x40
[   15.492334] [<ffffff800876a33c>] bus_add_driver+0x16c/0x270
[   15.497933] [<ffffff800876c430>] driver_register+0x68/0x100
[   15.503533] [<ffffff800876d9e4>] __platform_driver_register+0x5c/0x68
[   15.509926] [<ffffff80097e7f38>] trusty_virtio_driver_init+0x18/0x20
[   15.516141] [<ffffff8008083a9c>] do_one_initcall+0x44/0x128
[   15.521915] [<ffffff8009790cec>] kernel_init_freeable+0x198/0x22c
[   15.528475] [<ffffff8008e82918>] kernel_init+0x18/0x100
[   15.533722] [<ffffff80080838a0>] ret_from_fork+0x10/0x30
[   15.539129] trusty_ipc virtio0: vring0: va(pa)  ffffffc1e345e000(0) qsz 32 notifyid 1
[   15.546812] trusty_ipc virtio0: vring1: va(pa)  ffffffc1e3470000(0) qsz 32 notifyid 2

Maybe you can use your old topic to track, If they are using same command to hit this.