GitLab

under bad reception MM eventually discards the modem completely:

Okt 01 17:38:26 pureos ModemManager[507]: <info>  [modem0/call0] user request to hangup call
Okt 01 17:38:26 pureos ModemManager[507]: <info>  [modem0/call0] user request to hangup call
Okt 01 17:38:26 pureos ModemManager[507]: <info>  [modem0/call0] user request to hangup call
Okt 01 17:38:27 pureos ModemManager[507]: <info>  [modem0/call0] user request to hangup call
Okt 01 17:38:27 pureos ModemManager[507]: <info>  [modem0/call0] user request to hangup call
Okt 01 17:38:39 pureos calls[838]: Error hanging up ModemManager call to `+49xxxxxxxxxxx': Zeitüberschreitung wurde erreicht
...
Okt 01 17:39:15 pureos ModemManager[507]: <warn>  [modem0/call0] couldn't start call: Serial command timed out
Okt 01 17:39:15 pureos ModemManager[507]: <info>  [modem0/call0] call state changed: dialing -> terminated (unknown)
Okt 01 17:39:15 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 2 consecutive times
Okt 01 17:39:20 pureos ModemManager[507]: <warn>  [modem0] couldn't load call list: Serial command timed out
Okt 01 17:39:20 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 3 consecutive times
Okt 01 17:39:22 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 4 consecutive times
Okt 01 17:39:24 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 5 consecutive times
Okt 01 17:39:26 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 6 consecutive times
Okt 01 17:39:30 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 8 consecutive times
Okt 01 17:39:32 pureos ModemManager[507]: <warn>  [modem0] port ttyUSB1 timed out 9 consecutive times
Okt 01 17:39:34 pureos ModemManager[507]: <error> [modem0] port ttyUSB1 timed out 10 consecutive times, marking modem as invalid

Signal strength icon then disappears from the shell and only a killswitch off/on brings it back. I wonder if the modem firmware crashes here. (i had seen this before but could now gather logs)