After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 733086 - Ericsson F5321gw doesn't work after suspend/resume
Ericsson F5321gw doesn't work after suspend/resume
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: ModemManager
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-07-12 09:50 UTC by Tore Anderson
Modified: 2014-10-14 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ModemManager debug log (403.20 KB, text/plain)
2014-07-12 09:50 UTC, Tore Anderson
Details

Description Tore Anderson 2014-07-12 09:50:08 UTC
Created attachment 280544 [details]
ModemManager debug log

My Ericsson F5321gw MBM (OEM-ed as "HP hs2350 HSPA+") does not work properly after my laptop has been suspended/resumed. It appears that ModemManager fails to enable the modem, and mmcli fails thusly:

$ sudo mmcli -m 0 --simple-connect=apn=telenor.mobil,ip-type=ipv6
error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.libmbim.Error.Core.Timeout: Transaction timed out'

Restarting ModemManager fixes the problem and brings the modem back to life.

The attached file contains both the output from "mmcli -m 0" and "journalctl -u systemd-suspend.service -u ModemManager.service -b" (with MM log level debug). After the initial boot, the modem was left disabled (connecting after a boot does work just fine though). At 11:31:55 the system was suspended and resumed shortly after, followed by the failed simple-connect attempt shown above. At 11:34:03 I ran "systemctl restart ModemManager.service" followed by a repeat of the simple-connect attempt, this time successful.

Both ModemManager and libmbim are git master from today (20140712).
Comment 1 Aleksander Morgado 2014-07-13 11:15:32 UTC
I believe Bjorn already reported this. Basically, when suspending ModemManager keeps the state of the modem (MBIM open), but the modem itself gets fully reseted and needs an explicit new MBIM open. The error that you get during the connect call is actually:

[/dev/cdc-wdm1] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 16
>>>>>>   type        = function-error (0x80000004)
>>>>>>   transaction = 12
>>>>>> Contents:
>>>>>>   error = 'NotOpened' (0x00000005)

We should try to detect this case, and if so, mark the modem as invalid and fully re-probe from the beginning...
Comment 2 Aleksander Morgado 2014-10-14 12:31:59 UTC
Moving bugreport to the new ModemManager bugzilla in fd.o; summarized the issue
there as well. Please subscribe to the new bugreport to get new updates.

https://bugs.freedesktop.org/show_bug.cgi?id=84994

Closing this report as NOTGNOME.