Hi Aleksander, that's clear but as you can see in the logs the device does respond to AT commands in the problematic case. You can see that there are replies for AT#PORTCFG? on ttyACM0 and yet for some reason after a while MM decides to use mainly ttyACM3 and starts to act like ttyACM0 wasn't there.
Best regards, Piotr. 2017-06-28 10:59 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>: > On Wed, Jun 28, 2017 at 10:54 AM, Piotr Figiel <fig...@gmail.com> wrote: >> thanks for reply. >> Yes I could but I think it races with NM which tries to reestablish >> connection, not sure if such testcase will help to debug this. >> I've done some checks with with nmcli d disconnect ttyACM0 and it >> improved (though I'll redo this more systematically), but the problem >> may still be in MM and can trigger in case the modem suffers >> spontaneous restart (or is reconnected on USB). > > If the modem restarts and doesn't reply to the AT commands we send to > the TTY, there's not much we can do... :/ > > -- > Aleksander > https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
