Thanks on the input.
In this case it seems to be in a permanently stuck state and no
communication whatsoever.
Will check for any other symptoms leading to this state.
Thanks,
Ratnavel
On Wed, Jul 15, 2020 at 12:36 PM Bjørn Mork wrote:
> Aleksander Morgado writes:
>
> >>
> >> WARNING: CPU:
- 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*
Aleksander Morgado 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
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
a Sierra Wireless
> EM74xx modem
> >
> > Couldn't load extended signal information: No way to load extended
> signal information
> > ModemManager[1222]: Couldn't load extended signal information:
> Couldn't peek QMI port
> > ModemManager[1222]: Reloading stats fa
QMI port
> ModemManager[1222]: Reloading stats failed: QMI operation failed:
> Transaction timed out
>
> After this error, the ModemManager doesn't recover until a modem reset is
> performed. The modem is in a kind of locked state.
>
> The IP is still existing
stats failed: QMI operation failed:
Transaction timed out*
After this error, the ModemManager doesn't recover until a modem reset is
performed. The modem is in a kind of locked state.
The IP is still existing and restarting the ModemManager or the system is
not helping out.
What does the above
