Bug 102713

Summary: Sierra EM7345: First attempt to connect fails with 'cancelled', subsequent fail with OperationNotSupported
Product: ModemManager Reporter: dimitris
Component: mmcliAssignee: ModemManager bug user <modemmanager>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: 1.6   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: log from 1st attempt (cancelled)
log from 2nd attempt (operation not allowed)

Description dimitris 2017-09-13 21:57:01 UTC
Created attachment 134204 [details]
log from 1st attempt (cancelled)

Project Fi data-only SIM.  Worked, briefly, a day ago on this device, hasn't since.  SIM still works on another device (Nexus 5X).

> $ lsusb |grep Sierra
> Bus 002 Device 003: ID 1199:a001 Sierra Wireless, Inc.

> $ mmcli -m 0
> 
> /org/freedesktop/ModemManager1/Modem/0 (device id '2c05a513b579a5a5c2531b9bbc8d5a66237d8239')
>   -------------------------
>   Hardware |   manufacturer: 'Sierra'
>            |          model: 'MBIM [1199:A001]'
>            |       revision: 'FIH7160_V1.2_WW_01.1528.04'
>            |      supported: 'gsm-umts, lte'
>            |        current: 'gsm-umts, lte'
>            |   equipment id: ...
> -------------------------
>   System   |         device: '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4'
>            |        drivers: 'cdc_acm, cdc_mbim'
>            |         plugin: 'Sierra'
>            |   primary port: 'cdc-wdm0'
>            |          ports: 'wwp0s20u4 (net), cdc-wdm0 (mbim), ttyACM0 (at)'
>   -------------------------
>   Numbers  |           own : ...
> -------------------------
>   Status   |           lock: 'none'
>            | unlock retries: 'sim-pin2 (10)'
>            |          state: 'registered'
>            |    power state: 'on'
>            |    access tech: 'lte'
>            | signal quality: '9' (recent)
>   -------------------------
>   Modes    |      supported: 'allowed: 2g, 3g, 4g; preferred: none'
>            |        current: 'allowed: 2g, 3g, 4g; preferred: none'
>   -------------------------
>   Bands    |      supported: 'unknown'
>            |        current: 'unknown'
>   -------------------------
>   IP       |      supported: 'ipv4, ipv6, ipv4v6'
>   -------------------------
>   3GPP     |           imei: ...
>            |  enabled locks: 'fixed-dialing'
>            |    operator id: '310260'
>            |  operator name: 'T-Mobile'
>            |   subscription: 'unknown'
>            |   registration: 'home'
>   -------------------------
>   SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'
> 
>   -------------------------
>   Bearers  |          paths: 'none'

> $ mmcli -m 0 --simple-connect="apn=h2g2"
> error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Cancelled: Connection setup operation has been cancelled'

followed by:

> $ mmcli -m 0 --simple-connect="apn=h2g2"
> error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.libmbim.Error.Status.OperationNotAllowed: OperationNotAllowed'
Comment 1 dimitris 2017-09-13 21:57:39 UTC
Created attachment 134205 [details]
log from 2nd attempt (operation not allowed)
Comment 2 dimitris 2017-09-13 21:58:34 UTC
Forgot to add: This is on a Thinkpad X250, Fedora 26 running kernel 4.12.11-300.fc26.x86_64
Comment 3 dimitris 2017-09-14 16:40:14 UTC
Update: If I `systemctl restart ModemManager.service` I can (sometimes) connect again.  I'm adding this comment over the LTE connection.  Next time I reproduce I'll update the logs.
Comment 4 GitLab Migration User 2018-06-10 09:05:43 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/71.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.