Canonical System Image

Bug #1435328
Comment #38

Comment 38 for bug 1435328

Revision history for this message

Tony Espy (awe) wrote on 2015-04-22:

#38

@Alfonso

Regarding comment #26, to be clear, your exact scenario was this:

1. Install SIM with no data credit in slot1; this connection comes up, but any attempt to send/receive data fails
2. Activate WiFi, and wait till it associates with an AP
3. Disable WiFi
( this forces a disconnect of the modem, and the corresponding route configuration fails )

What I see from the logs is the Netlink failures, at which point I also see the NM device state go from activated to failed ( reason: ip-config-unavailable ). NM tries context1 ( 'Internet movil' ) again and it fails the next time due to 'no-secrets', which seems odd. It then moves on and tries context3 ( '___ubuntu custom internet apn' w/a null APN name ) and each time it fails with reason = 'modem-no-carrier'. This is odd, as I only ever see a single 'now in state registered' ( output by nm-modem-ofono.c::update_ofono_enabled() ), and never see the modem become unregistered ( which happens when Online, Attached or Powered go FALSE ).

Looking at the NM ofono activation code, although the error printed is "could not activate context, modem is not registered', the code actually just checks whether the modem is in REGISTERED state when it tries to connect. It's possible that the modem state is still CONNECTED, and somehow this didn't get reset to REGISTERED when the Netlink errors occurred? The modem state is only set back to REGISTERED in disconnect_done () and update_ofono_enabled (). Perhaps in this case, since the modem state isn't reset, the subsequent activation attempts will all fail.

If you can still reliably reproduce, could you turn on NM debug logging ( sudo nmcli general logging level debug ) and try to reproduce again and provide system logs. I will also try to force a modem disconnect ( via tinfoil wrapping ), and see what happens on vivid.

This theory also provides more weight to the thought that this is a vivid-only issue with NM, as the ofono modem state code is radically different in NM 0.9.8.

@Alfonso

Regarding comment #26, to be clear, your exact scenario was this:

What I see from the logs is the Netlink failures, at which point I also see the NM device state go from activated to failed ( reason: ip-config-unavailable ).  NM tries context1 ( 'Internet movil' ) again and it fails the next time due to 'no-secrets', which seems odd.  It then moves on and tries context3 ( '___ubuntu custom internet apn' w/a null APN name ) and each time it fails with reason = 'modem-no-carrier'.  This is odd, as I only ever see a single 'now in state registered' ( output by nm-modem-ofono.c::update_ofono_enabled() ), and never see the modem become unregistered ( which happens when Online, Attached or Powered go FALSE ).

Looking at the NM ofono activation code, although the error printed is "could not activate context, modem is not registered', the code actually just checks whether the modem is in REGISTERED state when it tries to connect.  It's possible that the modem state is still CONNECTED, and somehow this didn't get reset to REGISTERED when the Netlink errors occurred?  The modem state is only set back to REGISTERED in disconnect_done () and update_ofono_enabled ().  Perhaps in this case, since the modem state isn't reset, the subsequent activation attempts will all fail.

If you can still reliably reproduce, could you turn on NM debug logging ( sudo nmcli general logging level debug ) and try to reproduce again and provide system logs.  I will also try to force a modem disconnect ( via tinfoil wrapping ), and see what happens on vivid.

This theory also provides more weight to the thought that this is a vivid-only issue with NM, as the ofono modem state code is radically different in NM 0.9.8.