ModemManager watching suspend/resume events

Aleksander Morgado aleksander at aleksander.es
Sat Feb 7 03:59:50 PST 2015


On Tue, Jan 27, 2015 at 10:38 AM, Aleksander Morgado
<aleksander at aleksander.es> wrote:
> On Mon, Jan 26, 2015 at 11:45 PM, Dan Williams <dcbw at redhat.com> wrote:
>>> > However, I can still reproduce the issues.
>>> >
>>> > Attached a new log. I did the following:
>>> >
>>> > 13:25:00 initiate connection
>>> > 13:25:03 connection established
>>> > 13:25:13 suspend
>>> > 13:25:29 resume
>>> > 13:25:41 initiate connection via nm-applet
>>> > 13:26:41 timeout (modem still visible)
>>> > 13:27:06 restart ModemManager
>>> > 13:27:26 restart ModemManager done (modem now invisible)
>>> > 13:27:47 unbind, sleep 1, rebind modem
>>> > 13:28:00 connection established
>>>
>>>
>>> Florian, could you retry with the "'aleksander/suspend-resume' branch"
>>> in git? Please configure using --with-suspend-resume=systemd (or
>>> --with-suspend-resume=upower if you're not using systemd).
>>
>> I tried this out today with a QMI device and it worked for me, dropping
>> and successfully re-detecting all the ports correctly.
>
> I'll get this rebased and merged to git master during this week.


Merged to git master now.

-- 
Aleksander
https://aleksander.es


More information about the ModemManager-devel mailing list