Bearer removed but somehow stays active and blocks device (ref bug #17666)

[Aleksander Morgado]

On Fri, May 8, 2015 at 11:41 AM, Torsten Hilbrich
<torsten.hilbrich at secunet.com> wrote:
> Here is a problem that we received with a slightly older version:
>
> modemmanager: 1.4.0
> libmbim: 1.10.0
> libqmi: 7220aeafeca42b12482ac187374ecf3db40fa7cd on qmi-1.10 branch
>
> Here the following problem occured. The bearer/10 was disconnected and a
> new bearer created:
>
> <debug> [1430930918.632975] Disconnecting bearer
> '/org/freedesktop/ModemManager1/Bearer/10'
> <info>  [1430930918.633005] Modem
> /org/freedesktop/ModemManager1/Modem/9: state changed (connected ->
> disconnecting)
> <debug> [1430930918.633204] Launching disconnection on data port (net/wwan0)
> ...
> <debug> [1430930918.640844] Session ID '0' already disconnected.
> <debug> [1430930918.640855] (wwan0): port now disconnected
>
> Then a new bearer/11 is created and fails to connect:
>
> <debug> [1430930932.928234] New bearer created at DBus path
> '/org/freedesktop/ModemManager1/Bearer/11'
> ...
> <debug> [1430930932.952574] Error listing provisioned contexts:
> NoDeviceSupport
> ...
> <debug> [1430930932.960720] Couldn't connect bearer
> '/org/freedesktop/ModemManager1/Bearer/11': 'MaxActivatedContexts'
>
> Any idea, what might here the problem?
>
> Available log file is attached (compressed because of large size) , it
> seems that the logs were already rotated so no complete information from
> the startup are available. The notebook is a Lenovo T430 with Lenovo
> H5321 gw UMTS modem.
>
> Kernel is 3.19.1, here is the output of the cdc_mbim:
>
> cdc_acm 3-4:1.1: ttyACM15: USB ACM device
> cdc_acm 3-4:1.3: ttyACM17: USB ACM device
> cdc_wdm 3-4:1.5: cdc-wdm0: USB WDM device
> cdc_mbim 3-4:1.6: cdc-wdm1: USB WDM device
> cdc_mbim 3-4:1.6 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-4, CDC
> MBIM, 6a:58:b1:bb:ac:07
> cdc_wdm 3-4:1.8: cdc-wdm2: USB WDM device
> cdc_acm 3-4:1.9: ttyACM18: USB ACM device
>

This looks like it could be a firmware issue in the modem itself,
given that it ends up returning NoDeviceSupport error when listing
provisioned contexts? Can you reproduce this easily? Is the issue
resolved if the modem device gets rebooted?

-- 
Aleksander
https://aleksander.es