Aleksander Morgado <aleksan...@aleksander.es> writes: >> >> 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.
Yes, this warning is expected if the modem is stuck. But I'd like to note that the warning by itself doesn't necessarily imply that a permanently stuck modem. It can be triggered under normal conditions for radio devices. The warning just says that the TX queue had to be stopped for more than 5 seconds. This can happen e.g. due to temporary radio network issues. The driver doesn't know whether the modem is stuck for 6 seconds or forever when issuing the warning. Of course, in this case there are other indications that the modem firmware has locked up, and the warning is definitely a symptom of that lockup. Just trying to add some extra context for future google searches :-) Some people are worried when they see that warning from an otherwise working modem. There is no reason to worry in such cases. It is perfectly normal and harmless. Bjørn _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
