Sierra EM7305: MaxActivatedContexts

[Florian Klink]

Hi Aleksander,

Am 05.11.2014 um 14:28 schrieb Aleksander Morgado:
> On Wed, Nov 5, 2014 at 1:46 PM, Florian Klink <flokli at flokli.de> wrote:
>> Today when I tried to use my modem, I was unable to connect successfully.
>>
>> It seems like the modem was (internally) connected, but ModemManager
>> thought it was disconnected. "ip a" showed no ip address.
>>
>> I attached the syslog.
>>
>> Does this make any sense to you?
> 
> 
> The "Transaction timed out" log doesn't make any sense, because all
> commands in the MBIM bearer connection sequence have some pretty long
> timeout values.
> 
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info> Activation
> (cdc-wdm0) starting connection 'O2 Pay-by-MB'
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info> Activation
> (cdc-wdm0) Stage 1 of 5 (Device Prepare) scheduled...
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info> Activation
> (cdc-wdm0) Stage 1 of 5 (Device Prepare) started...
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info> (cdc-wdm0):
> device state change: disconnected -> prepare (reason 'none') [30 40 0]
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info>
> NetworkManager state is now CONNECTING
> Nov 05 09:52:35 flokli-fujitsu NetworkManager[575]: <info> Activation
> (cdc-wdm0) Stage 1 of 5 (Device Prepare) complete.
> Nov 05 09:52:35 flokli-fujitsu ModemManager[573]: <info>  Simple
> connect started...
> Nov 05 09:52:35 flokli-fujitsu ModemManager[573]: <info>  Simple
> connect state (4/8): Wait to get fully enabled
> Nov 05 09:52:36 flokli-fujitsu ModemManager[573]: <info>  Modem
> /org/freedesktop/ModemManager1/Modem/0: state changed (disconnecting
> -> registered)
> Nov 05 09:52:36 flokli-fujitsu ModemManager[573]: <info>  Simple
> connect state (5/8): Register
> Nov 05 09:52:36 flokli-fujitsu ModemManager[573]: <info>  Simple
> connect state (6/8): Bearer
> Nov 05 09:52:36 flokli-fujitsu ModemManager[573]: <info>  Simple
> connect state (7/8): Connect
> Nov 05 09:52:36 flokli-fujitsu ModemManager[573]: <info>  Modem
> /org/freedesktop/ModemManager1/Modem/0: state changed (registered ->
> connecting)
> Nov 05 09:52:36 flokli-fujitsu NetworkManager[575]: <info> (cdc-wdm0):
> modem state changed, 'disconnecting' --> 'registered' (reason:
> user-requested)
> Nov 05 09:52:36 flokli-fujitsu NetworkManager[575]: <warn> (cdc-wdm0)
> failed to connect modem: Transaction timed out
> Nov 05 09:52:36 flokli-fujitsu NetworkManager[575]: <info> (cdc-wdm0):
> device state change: prepare -> failed (reason '(null)') [40 120 1]
> Nov 05 09:52:36 flokli-fujitsu NetworkManager[575]: <info>
> NetworkManager state is now DISCONNECTED
> 
> Are you able to reproduce this easily? If so, could you gather debug logs?
> http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
> 

I wasn't able to reproduce it so far. But something seems to be really
borked with this modem. It currently only wants to connect to "EDGE
(ETSI 27.007: "GSM w/EGPRS")" according to modem-manager-gui, although
it's in an area with at least HSDPA, if not LTE (I have a SIM Card from
the same operator in a smartphone directly nearby)...

It seems like setting the allowed modes in nm-connection-editor doesn't
do anything, as `mmcli -m 12 --set-allowed-modes=ANY` says:
> error: couldn't set current modes:
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported:
Setting allowed modes not supported'

I changed NetworkManager and ModemManagers unit files to log debug
information, and will try to post a log of a new connection in an area
with very good LTE coverage later today.


-- 
Florian Klink

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/modemmanager-devel/attachments/20141107/af4bb75a/attachment.sig>