<html><head></head><body><div class="ydp771a87e5yahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:13px;"><div id="ydp771a87e5yiv6815333111"><div class="ydp771a87e5yiv6815333111yahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><div>I'm having this same issue with MM 1.10.0<br></div><div>Has it been fixed? In which version if so?</div><div><br></div><div>Cheers, Sam.</div><div><br></div><div>> Matthew Starr mstarr at hedonline.com</div><div>> Thu Jul 19 19:21:41 UTC 2018</div><div>></div><div>> > -----Original Message-----</div><div>> > From: Aleksander Morgado [mailto:aleksander at aleksander.es]</div><div>> > Sent: Thursday, July 19, 2018 2:16 PM</div><div>> > </div><div>> > Hey,</div><div>> > </div><div>> > On Thu, Jul 19, 2018 at 3:47 PM, Matthew Starr <mstarr at hedonline.com></div><div>> > wrote:</div><div>> > > I am running ModemManager 1.8.0 and NetworkManager 1.8.0 on an</div><div>> > embedded device with the Linux OS built by buildroot. I am using a u-blox</div><div>> > TOBY-R200 cell modem connected over USB with virtual serial interfaces</div><div>> > /dev/ttyACM0 through /dev/ttyACM5.</div><div>> > ></div><div>> > > Sometimes while connected to the cellular network for a longer period of</div><div>> > time (sometimes around 200 minutes, other times I have reached over 800</div><div>> > minutes), ModemManager will report a modem hangup that was not</div><div>> > initiated by user action or loss of signal since this is a stationary device that is</div><div>> > being tested. Usually ModemManager will reconnect with NetworkManager</div><div>> > prompting for the associated cell profile to be reconnected. My issue is that</div><div>> > sometimes no matter how many times I try or auto reconnects are tried,</div><div>> > ModemManager cannot reestablish a data connection. ModemManager just</div><div>> > keeps reporting that it can't open /dev/ttyACM0 which is was using just fine</div><div>> > before. The interesting thing is that if I restart ModemManager, it is able to</div><div>> > open the /dev/ttyACM0 port right away and make a data connection again,</div><div>> > so it doesn't look to be an issue with the modem causing serial port issues.</div><div>> > This looks to be some sort of serial port handling issue in ModemManager,</div><div>> > maybe just related to u-blox but I am not sure. I looked at the state of the</div><div>> > /dev/ttyACM0 device using lsof and it is not reporting that any other process</div><div>> > has that device file open or locked.</div><div>> > ></div><div>> > </div><div>> > These seem relevant, yes:</div><div>> > </div><div>> > > Jul 19 12:52:31 canect2 daemon.warn ModemManager[302]: <warn></div><div>> > Couldn't load Operator Code: 'Cannot run sequence: 'Could not open serial</div><div>> > device ttyACM0: it has been forced close''</div><div>> > > Jul 19 12:52:31 canect2 daemon.warn ModemManager[302]: <warn></div><div>> > Couldn't load Operator Name: 'Cannot run sequence: 'Could not open serial</div><div>> > device ttyACM0: it has been forced close''</div><div>> > ...</div><div>> > </div><div>> > Any chance you can get a debug output of MM while reproducing this issue?</div><div>> </div><div>> I will try to run with debug turned on, but it does not happen all the time. I will send an update when and if I can get it to happen with debug turned on.</div><div>> </div><div>> Best regards,</div><div>> Matthew Starr</div></div><br><br></div></div></div></div></body></html>