Originally reported at: https://bugs.freedesktop.org/show_bug.cgi?id=84994 Please refer to the original bug report if more details are needed. This bug re-procedure at [Snappy] ModemManager 1.6.2-4. Snappy Ubuntu core 16 When hibernating, ModemManager keeps the state of the modem (MBIM open), but the modem itself gets fully reset and needs an explicit new MBIM open, or otherwise the MBIM port will keep on saying that it was not opened.
(In reply to Samuel HUI from comment #0) > Originally reported at: > https://bugs.freedesktop.org/show_bug.cgi?id=84994 > Please refer to the original bug report if more details are needed. > > This bug re-procedure at [Snappy] ModemManager 1.6.2-4. > Snappy Ubuntu core 16 > > When hibernating, ModemManager keeps the state of the modem (MBIM open), but > the modem itself gets fully reset and needs an explicit new MBIM open, or > otherwise the MBIM port will keep on saying that it was not opened. The detection of suspend/resume in order to have MM reopen the ports requires configure to run with the optional --with-suspend-resume=systemd option. Is ModemManager being built in that way?
Hi Aleksander, Thank you for your reply. As for the ModemManager package is built by developer "canonical" and included in the Snappy Ubuntu Core 16 installation package. I don't know the optional --with-suspend-resume=system option is configured or not. Do you have any suggestion how to find a built version have solved this issue? Thanks in advance.
> > Do you have any suggestion how to find a built version have solved this > issue? > Run ModemManager in debug mode, see: https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ And run some suspend/resume cycles while the debug log is being generated. If the suspend-resume is working you should see debug logs prefixed with "[sleep-monitor]".
Hi Aleksamder, Thank you for your reply. I will run the ModemManager in debug mode to see the ModemManager which we use is support the suspend -resume. Thank you!
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/36.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.