- The device did stop communicating after that (including the QMI commands). - 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. - It got stuck forever. - Firmware version - EM74xx - *02.24.05.06*
Planning to upgrade to *02.33.03.00* Any other pointers to confirm this is a modem firmware issue? Thanks, Ratnavel On Wed, Jul 15, 2020 at 12:16 PM Aleksander Morgado < aleksan...@aleksander.es> wrote: > Hey! > > > > > WARNING: CPU: 1 PID: 0 at /linux-4.10.0/net/sched/sch_generic.c:316 > dev_watchdog+0x22c/0x230 > > NETDEV WATCHDOG: wwp0s (qmi_wwan): transmit queue 0 timed out > > > > Oh well, the infamous "transmit queue 0 timed out" error... That is, > as far as I know, a clear indication of a modem firmware problem; the > device stopped responding in the USB layer, so the device is probably > stuck. This also explains why you didn't get the response to the stats > query, the device stopped sending info in the USB layer. > > Did the device keep the data communication after this happened? Or did > only the QMI commands get stopped? > Did the device at least reboot itself after some seconds? Or did it > get stuck forever? I've seen devices doing both kind of things. > What EM74xx firmware version are you using? If not the newest one, > maybe try upgrading? > > -- > Aleksander > https://aleksander.es >
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
