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

[Torsten Hilbrich]

On 09.05.2015 16:51, Aleksander Morgado wrote:
...
>> 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?
...

> 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?
> 

This is not easily reproducible, the problem was only reported once so
far. The problem went away when rebooting the system.

	Torsten Hilbrich