# EM9190 cdc\_mbim 4-3:1.0 wwan0: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out

**URL:** <https://forum.sierrawireless.com/t/em9190-cdc-mbim-4-3-1-0-wwan0-netdev-watchdog-cpu-0-transmit-queue-0-timed-out/35641>\
**Category:** MC/EM Series\
**Tags:** driver\
**Created:** [November 28, 2025, 10:09am UTC](https://forum.sierrawireless.com/t/em9190-cdc-mbim-4-3-1-0-wwan0-netdev-watchdog-cpu-0-transmit-queue-0-timed-out/35641 "2025-11-28T10:09:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wannes](https://avatars.discourse-cdn.com/v4/letter/w/e9a140/32.png) [@wannes](https://forum.sierrawireless.com/u/wannes)\
**Post date:** [November 28, 2025, 10:09am UTC](https://forum.sierrawireless.com/t/em9190-cdc-mbim-4-3-1-0-wwan0-netdev-watchdog-cpu-0-transmit-queue-0-timed-out/35641/1 "2025-11-28T10:09:01Z")

</div>

Hi

I have a EM9190 modem running in USB mode. The used driver is `cdc_mbim`. My current firmware is `03.09.03.00_ORANGE`. It is working as expected, but after running for several hours, the firmware seemed to crash. `dmesg` returned the following:

`cdc_mbim 4-3:1.0 wwan0: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out 5132 ms`

Any ideas on how to debug or fix this are much appreciated!

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 28, 2025, 10:18am UTC](https://forum.sierrawireless.com/t/em9190-cdc-mbim-4-3-1-0-wwan0-netdev-watchdog-cpu-0-transmit-queue-0-timed-out/35641/2 "2025-11-28T10:18:23Z")

</div>

you can see here:

> [@Setting up EM9291 Module](https://forum.sierrawireless.com/t/setting-up-em9291-module/35558/14):
>
> cdc-mbim is generic driver in linux, it is not from Semtech. You can validate the module in Ubuntu linux PC. If it works, then it is your raspberry pi board problem. BTW, other user did not find problem on MBIM interface with Raspberry pi board:

You need to check the full dmesg log to see whether module has really rebooted
