#1123659 modemmanager: Quectel EM120R_GL does not connect after hibernation

Package:
modemmanager
Source:
modemmanager
Description:
D-Bus service for managing modems
Submitter:
Phenix
Date:
2025-12-19 16:07:03 UTC
Severity:
normal
#1123659#5
Date:
2025-12-19 16:05:55 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***


   * What led up to the situation?
Connection usually works, even after suspend and resume but not after
hibernation.


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Following steps were necessary to make this Modem work in the first place:
- Followed official Lenovo install path: https://snapcraft.io/install/lenovo-
wwan-dpr/debian
- Also activation over Windows seemed necessary for Debian to recognize vendor
Locked SIM.

To reproduce the issue:
After effective installation, swap hibernate was activated and gnome Hibernate
Status Button by slaclau https://extensions.gnome.org/extension/755/hibernate-
status-button/ was added.

Hibernation works and resume also, but modem does not connect to network after
hibernation.


   * What was the outcome of this action?
journalctl -u ModemManager
Dec 19 15:41:49 phenix-20xy0041mz ModemManager[1082]: <msg> [sleep-monitor-
systemd] system is about to suspend
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [/dev/wwan0mbim0]
MBIM error: Transaction timed out
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [/dev/wwan0mbim0]
MBIM error: Transaction timed out
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [/dev/wwan0mbim0]
MBIM error: Transaction timed out
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [/dev/wwan0mbim0]
MBIM error: Transaction timed out
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [/dev/wwan0mbim0]
MBIM error: Transaction timed out
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <msg> [sleep-monitor-
systemd] system is resuming
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [plugin-manager]
task 2: port context already scheduled
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [plugin-manager]
task 2: port context already scheduled
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [plugin-manager]
task 2: port context already scheduled
Dec 19 15:42:42 phenix-20xy0041mz ModemManager[1082]: <wrn> [plugin-manager]
task 2: port context already scheduled
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0at0/probe]
probe step: start
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0at0/probe]
probe step: AT open port
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0mbim0/probe]
probe step: start
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0mbim0/probe]
probe step: MBIM
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0qcdm0/probe]
probe step: start
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0qcdm0/probe]
probe step: QCDM
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0qcdm0/probe]
probe step: done
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0at0/probe]
probe step: AT
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0mbim0/mbim]
Skipping QMI support check in MBIM device
Dec 19 15:42:44 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0mbim0/probe]
probe step: done
Dec 19 15:42:45 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0at0/probe]
probe step: AT close port
Dec 19 15:42:45 phenix-20xy0041mz ModemManager[1082]: <msg> [wwan0at0/probe]
probe step: done
Dec 19 15:42:46 phenix-20xy0041mz ModemManager[1082]: <msg> [device
/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0] creating modem with plugin
'quectel' and '4' ports (1eac:1eac:1001)
Dec 19 15:42:46 phenix-20xy0041mz ModemManager[1082]: <msg> [base-manager]
modem for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'
successfully created
Dec 19 15:42:46 phenix-20xy0041mz ModemManager[1082]: <msg> [base-manager]
running setup for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0'...
Dec 19 15:42:46 phenix-20xy0041mz ModemManager[1082]: <msg> [base-manager]
couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not
supported by any plugin
Dec 19 15:42:46 phenix-20xy0041mz ModemManager[1082]: <msg>
[modem1/wwan0mbim0/mbim] MBIM device is QMI capable
Dec 19 15:42:47 phenix-20xy0041mz ModemManager[1082]: <wrn> Left '18' bytes
unread when getting the 'Slot EID' TLV
Dec 19 15:42:47 phenix-20xy0041mz ModemManager[1082]: <wrn> Left '18' bytes
unread when getting the 'Slot EID' TLV
Dec 19 15:42:47 phenix-20xy0041mz ModemManager[1082]: <msg>
[modem1/wwan0mbim0/mbim] (shared-quectel) MBIM device is AT capable
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (unknown -> disabled)
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (disabled -> enabling)
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect started...
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect state (4/10): wait to get fully enabled
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] couldn't
enable interface: 'Invalid transition'
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (enabling -> disabled)
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] failed
waiting for enabled state: disabled
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] failed
enabling modem: Invalid transition
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect started...
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect state (3/10): enable
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (disabled -> enabling)
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect started...
Dec 19 15:42:49 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect state (4/10): wait to get fully enabled
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] couldn't
enable interface: 'Invalid transition'
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (enabling -> disabled)
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] failed
waiting for enabled state: disabled
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] failed
enabling modem: Invalid transition
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect started...
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect state (3/10): enable
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (disabled -> enabling)
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect started...
Dec 19 15:42:51 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] simple
connect state (4/10): wait to get fully enabled
Dec 19 15:42:53 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:53 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] Busy
Dec 19 15:42:53 phenix-20xy0041mz ModemManager[1082]: <wrn> [modem1] couldn't
enable interface: 'Invalid transition'
Dec 19 15:42:53 phenix-20xy0041mz ModemManager[1082]: <msg> [modem1] state
changed (enabling -> disabled)


   * What outcome did you expect instead?
The Modem to connect back to the network.