<div dir="ltr"><ul><li>The device did stop communicating after that (including the QMI commands).</li><li>The device did not reboot and no internal reset occurred. Only manual modem reset had to be done to bring it out of that state.</li><li>It got stuck forever.</li><li>Firmware version - EM74xx -
<span style="font-size:11pt;font-family:Calibri,sans-serif"><b>02.24.05.06</b></span></li></ul><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Planning to upgrade to </span></font><span style="font-family:Calibri,sans-serif;font-size:11pt"><b>02.33.03.00</b></span></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Any other pointers to confirm this is a modem firmware issue?</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Thanks,</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Ratnavel</span></font></div><div><span style="font-family:Calibri,sans-serif;font-size:11pt"><b><br></b></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 15, 2020 at 12:16 PM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey!<br>
<br>
><br>
> WARNING: CPU: 1 PID: 0 at /linux-4.10.0/net/sched/sch_generic.c:316 dev_watchdog+0x22c/0x230<br>
> NETDEV WATCHDOG: wwp0s (qmi_wwan): transmit queue 0 timed out<br>
><br>
<br>
Oh well, the infamous "transmit queue 0 timed out" error... That is,<br>
as far as I know, a clear indication of a modem firmware problem; the<br>
device stopped responding in the USB layer, so the device is probably<br>
stuck. This also explains why you didn't get the response to the stats<br>
query, the device stopped sending info in the USB layer.<br>
<br>
Did the device keep the data communication after this happened? Or did<br>
only the QMI commands get stopped?<br>
Did the device at least reboot itself after some seconds? Or did it<br>
get stuck forever? I've seen devices doing both kind of things.<br>
What EM74xx firmware version are you using? If not the newest one,<br>
maybe try upgrading?<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a><br>
</blockquote></div>