Help on an invalid modem case

[Louis-Alexis Eyraud]

Hi Aleksander,

here are the logs you ask:
  - mmcli and lsusb output logs
  - the matching Modem Manager debug logs

Hope it helps.
________________________________
From: Aleksander Morgado <aleksander at aleksander.es>
Sent: 03 July 2020 17:40
To: Louis-Alexis Eyraud <louis-alexis.eyraud at sigfox.com>
Cc: ModemManager (development) <modemmanager-devel at lists.freedesktop.org>
Subject: Re: Help on an invalid modem case

Hey,


my team and I are using for testing purposes an 3G USB modem (Huawei E352) that has an unexpected behaviour with ModemManager 1.12.10 and later stable versions (1.12.12 and 1.14.0).
The 3G modem is used as a broadband one and every time it disconnects, it encounters AT serial timeouts and is eventually declared as invalid by ModemManager then removed from modem list.

Jul 02 08:42:27.226342 tap-00006711 ModemManager[1225]: <debug> [1593679347.226334] (ttyUSB1): --> 'ATE0<CR>'
...
Jul 02 08:42:30.453896 tap-00006711 ModemManager[1225]: <debug> [1593679350.453872] (ttyUSB1): --> 'ATV1<CR>'
Jul 02 08:42:33.679831 tap-00006711 ModemManager[1225]: <warn>  [1593679353.679807] (tty/ttyUSB1) at port timed out 2 consecutive times
...
Jul 02 08:42:59.421551 tap-00006711 ModemManager[1225]: <error> [1593679379.421503] (tty/ttyUSB1) at port timed out 10 consecutive times, marking modem '/org/freedesktop/ModemManager1/Modem/0' as invalid
...
Jul 02 08:43:02.667893 tap-00006711 ModemManager[1225]: <debug> [1593679382.667880] Modem (Huawei) '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb4/4-1' completely disposed

Only an external action (unplug/unplug, electrical action) makes it reappear, manual scan via mmcli does not.

So I have two questions:
1) Is there something in the debug logs that may explain these systematic serial timeouts?
I'm not sure ModemManager is at fault here (like some actions leading to unrecoverable errors) or the modem device is simply defective...


When the ttyUSB being used for data doesn't cleanly disconnect, it may be because we're using the wrong TTY for data. What's the output of "mmcli -m 0" and the "lsusb -v" for the device?

2) When the modem is declared invalid, is a there a way using libmm-glib to detect or be notified of such event occurrences?
The device disappearance at ModemManager and NetworkManager level is an obvious one but since it is quite a common event, we would like to know if something more specific can be observed.


The device disappearance from MM would be the best way I'd say.

--
Aleksander
https://aleksander.es<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Faleksander.es%2F&data=02%7C01%7Clouis-alexis.eyraud%40sigfox.com%7Ca8f53fb654b04dac469f08d81f676629%7Cfcbc8bb1061e4b949f703ad917b0c8d3%7C0%7C0%7C637293876239957881&sdata=75llgC6RFJ4U3VcoIG8SPEj2Tzoi0hJX6QLkN4qkt7k%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200706/b9a5bd26/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ley_lsusb.log
Type: text/x-log
Size: 8242 bytes
Desc: ley_lsusb.log
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200706/b9a5bd26/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ley_mmcli.log
Type: text/x-log
Size: 1955 bytes
Desc: ley_mmcli.log
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200706/b9a5bd26/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ley_mm_debug_2.log
Type: text/x-log
Size: 193856 bytes
Desc: ley_mm_debug_2.log
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20200706/b9a5bd26/attachment-0005.bin>