[Bug 901122] New: Need to restart ModemManager after suspend-to-RAM for 3G/UMTS
http://bugzilla.suse.com/show_bug.cgi?id=901122 Bug ID: 901122 Summary: Need to restart ModemManager after suspend-to-RAM for 3G/UMTS Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This is latest Factory and an Ericsson Business Mobile Networks BV (ID 0bdb:1926) UMTS/3G card built into my notebook. The card works fine with openSUSE 13.1 and also Factory, just that on the latter I also had to add a file with options cdc_ncm prefer_mbim=N to /etc/modprobe.d (which was not necessary with the older kernel). However, whenever I suspend-to-RAM and resume I need to restart ModemManager with `systemctl restart ModemManager` or no connection can be established. (Bug #901041 may be related.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=901122 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |dimstar@opensuse.org, | |gp@suse.com Flags| |needinfo?(gp@suse.com) --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> --- To not loose all the information that was passed on the mailing listn continued from http://lists.opensuse.org/opensuse-gnome/2014-10/msg00023.html there seems to be a firmware issue in some cdc devices, that do not get reset properly after a reboot. We can try to add a restart-script in /usr/lib/systemd/system-sleep 50-restart_MM
- SNIP HERE - <<< #!/bin/sh case $1 in resume|thaw|post) /usr/bin/systemctl restart ModemManager.service > /dev/null ;; esac - SNIP HERE - <<<
Can you please verify if that helps you in any way? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=901122 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(gp@suse.com) | --- Comment #2 from Gerald Pfeifer <gp@suse.com> --- Sorry for the delay, this has proven hard to test. Doing some extensive testing over the last 24 hours I can confirm that with a similar script: case $1 in resume|thaw|post) sleep 10 ; /usr/bin/systemctl restart ModemManager.service > /dev/null ;; esac it mostly¹ works on Factory (kernel 3.17.4-1-default, ModemManager 1.4.0-1.1.x86_64). It does NOT WORK WITHOUT this script. ¹Mostly since I did have one failure after a longer suspend-to-RAM, where I had to restart ModemManager manually. That was one out of twenty cases, though, and other long suspensions did resume just fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=901122 --- Comment #3 from Gerald Pfeifer <gp@suse.com> --- In case you wonder about the sleep 10 before the ModemManager restart, without that (or a sleep 5, as I just tested), it does not work. In that case, the failure case, the log looks as follows: 2014-12-31T07:09:43.785237+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) starting connection ' Telkomsel' 2014-12-31T07:09:43.785553+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled... 2014-12-31T07:09:43.785765+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) started... 2014-12-31T07:09:43.785958+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0] 2014-12-31T07:09:43.786158+08:00 tuna NetworkManager[887]: <info> NetworkManager state is now CONNECTING 2014-12-31T07:09:43.788308+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0] 2014-12-31T07:09:43.788595+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete. 2014-12-31T07:09:43.794572+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled... 2014-12-31T07:09:43.804897+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) started... 2014-12-31T07:09:43.805129+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2014-12-31T07:09:43.805883+08:00 tuna NetworkManager[887]: <info> Activation (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete. 2014-12-31T07:09:43.830879+08:00 tuna NetworkManager[887]: <warn> (cdc-wdm0) failed to connect modem: Network timeout 2014-12-31T07:09:43.831168+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): device state change: prepare -> failed (reason 'gsm-registration-timeout') [40 120 32] 2014-12-31T07:09:43.831383+08:00 tuna NetworkManager[887]: <info> NetworkManager state is now DISCONNECTED 2014-12-31T07:09:43.831596+08:00 tuna NetworkManager[887]: <info> Disabling autoconnect for connection ' Telkomsel'. 2014-12-31T07:09:43.831806+08:00 tuna NetworkManager[887]: <warn> Activation (cdc-wdm0) failed for connection ' Telkomsel' 2014-12-31T07:09:43.833350+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0] 2014-12-31T07:09:43.833651+08:00 tuna NetworkManager[887]: <info> (cdc-wdm0): deactivating device (reason 'none') [0] To summarize: A ModemManager restart is required, either as part of a script like suggested by Dominique or manually. I must not happen too early after resuming from suspend-to-RAM. (No delay or 1 second is too early; 10 seconds works rather reliable, and 5 seconds seems to do it as well.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=901122 Jonathan Kang <sckang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sckang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com