ModemManager watching suspend/resume events

Florian Klink flokli at flokli.de
Sun Jan 11 14:08:42 PST 2015


Hi,

I think I'm also affected by this problem with my Sierra EM7305.

Currently I need to unbind and bind the usb device via the
/sys/bus/usb/drivers/usb/ interface to get it re-initialized by
NetworkManager, which is quite hacky.

Unfortunately, I'm not familiar enough with the
NetworkManager/ModemManager ecosystem to write any code for it, but I'd
be glad to help while testing some patches and providing debug logs
while suspending and resuming :-)

Florian


Am 11.01.2015 um 19:56 schrieb Aleksander Morgado:
> Hey,
> 
> Some MBIM modems will end up getting fully reseted during a
> suspend/resume cycle, and ModemManager may not be notified by the
> kernel of the ports being removed/readded. This ends up causing issues
> because the MBIM session is closed and ModemManager assumes it's open
> (and we get NotOpened errors).
> 
> I tried to handle that directly in ModemManager just by trying to
> reprobe from scratch the modem when we do detect the first NotOpened
> error, see:
> https://bugs.freedesktop.org/show_bug.cgi?id=84994
> 
> The branch has some bugs; but anyway I don't think it's the way to go.
> Instead of waiting for the first NotOpened error to happen (which may
> not happen quick enough if the modem is e.g. in Disabled state), we
> should instead listen for Suspend/Resume events and fully reload
> modems when that happens (code to do this is already ready in the
> branch), as we cannot assume that the state of the modem is the same
> as before the cycle.
> 
> Comments anyone? Anyone willing to help develop this? :)
> 
> Cheers!
> 


-- 
Florian Klink

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/modemmanager-devel/attachments/20150111/77b63712/attachment.sig>


More information about the ModemManager-devel mailing list