EM9291 sending disconnect request to the 5G core

Hi ,

If the EM9291 is connected for a longer period with the private 5G network.
It sends disconnection request and we get error:
[ 460.002831] ------------[ cut here ]------------
[ 460.007480] NETDEV WATCHDOG: wwan0 (cdc_mbim): transmit queue 0 timed out 8636 ms
[ 460.015062] WARNING: CPU: 1 PID: 0 at /net/sched/sch_generic.c:525 dev_watchdog+0x234/0x23c
[ 460.023430] Modules linked in: imx_rpmsg_tty vvcam_video(O) vvcam_isp(O) vvcam_dwe(O) imx8_media_dev(C) imx708(O) fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc c]
[ 460.059396] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C O 6.6.36+ #1
[ 460.066884] Hardware name: Arkenstone i.MX8MPlus LPDDR4 board (DT)
[ 460.073066] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=–)
[ 460.080032] pc : dev_watchdog+0x234/0x23c
[ 460.084044] lr : dev_watchdog+0x234/0x23c
[ 460.088058] sp : ffff80008000bde0
[ 460.091370] x29: ffff80008000bde0 x28: 0000000000000101 x27: ffff80008000be90
[ 460.098512] x26: ffff8000820969c0 x25: 00000000000021bc x24: ffff800082096000
[ 460.105655] x23: 0000000000000000 x22: ffff0000d112e3dc x21: ffff0000d112e000
[ 460.112800] x20: ffff0000d0e83400 x19: ffff0000d112e488 x18: 0000000000000006
[ 460.119944] x17: 36382074756f2064 x16: 656d697420302065 x15: 756575712074696d
[ 460.127086] x14: 736e617274203a29 x13: ffff8000820b1030 x12: 00000000000008b2
[ 460.134231] x11: 00000000000002e6 x10: ffff800082109030 x9 : ffff8000820b1030
[ 460.141372] x8 : 00000000ffffefff x7 : ffff800082109030 x6 : 80000000fffff000
[ 460.148518] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[ 460.155663] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000d01b8ec0
[ 460.162808] Call trace:
[ 460.165254] dev_watchdog+0x234/0x23c
[ 460.168920] call_timer_fn.isra.0+0x24/0x80
[ 460.173108] __run_timers+0x234/0x280
[ 460.176774] run_timer_softirq+0x20/0x40
[ 460.180700] handle_softirqs+0x108/0x24c
[ 460.184632] __do_softirq+0x14/0x20
[ 460.188122] ____do_softirq+0x10/0x1c
[ 460.191787] call_on_irq_stack+0x24/0x4c
[ 460.195714] do_softirq_own_stack+0x1c/0x2c
[ 460.199902] irq_exit_rcu+0xc0/0xdc
[ 460.203394] el1_interrupt+0x38/0x68
[ 460.206980] el1h_64_irq_handler+0x18/0x24
[ 460.211078] el1h_64_irq+0x64/0x68
[ 460.214480] cpuidle_enter_state+0x134/0x2e0
[ 460.218755] cpuidle_enter+0x38/0x50
[ 460.222341] do_idle+0x1f4/0x264
[ 460.225576] cpu_startup_entry+0x38/0x3c
[ 460.229501] secondary_start_kernel+0x130/0x150
[ 460.234039] __secondary_switched+0xb8/0xbc
[ 460.238228] —[ end trace 0000000000000000 ]—

Why the UE sends disconnection request?


Thanks,
Arti

Does the module reset?

Doesn’t seem like it.
It just gets disconnected.

Also is there a way to capture the UE logs? We are getting “Cause #36” from the UE.
DO we have any document with the list of codes and issues? anyway to capture the firmware logs?

Thanks,
Arti

you can use MBPL dm-logger to capture Qualcomm QXDM log.
After that you can contact distributor to do analysis.

From where I can find the source code of dm-logger. I need to build it for my hardware architecture.

Thanks

Please contact distributor to get the source code.