Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
Ubuntu 18.04, Thinkpad X240, Sierra modem
Reproduced on 4.15 and 4.18 kernel.
The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives:
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001]
And mmcli -m 9:
Status | lock: 'none'
| unlock retries: 'sim-pin (3)'
| state: 'registered'
| power state: 'on'
| access tech: 'gprs, lte'
| signal quality: '0' (cached)
After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again.
Similar to:
https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743
On Ubuntu 16.04 suspend and ModemManager used to work flawlessly.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jan 2384 F.... pulseaudio
/dev/snd/controlC1: jan 2384 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998
InstallationDate: Installed on 2016-10-22 (915 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20ALA0ARHH
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=pl_PL.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
RelatedPackageVersions:
linux-restricted-modules-4.18.0-18-generic N/A
linux-backports-modules-4.18.0-18-generic N/A
linux-firmware 1.173.5
Tags: bionic
Uname: Linux 4.18.0-18-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago)
UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET94WW (2.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ALA0ARHH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X240
dmi.product.name: 20ALA0ARHH
dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1826461
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.