This is pretty obvious by looking in the attached nmlog file, and search for connection '/208150102671184/context1'. You'll see it get disabled at 18:41:24 after a bunch of failed attempts ( modem-no-carrier ). It gets successfully auto-activated again in +5m.
That said, I also see something else that concerns me.
If you look at the netlog, after '/208150102671184/context1' is disabled, you'll see NM try a 'context3', 'context5', and 'context1' again. The odd thing is that the related IMSI is not '208150102671184' it's '208103698221268'. Looking at network-test-session.log ( also attached ), you'll see that '208150102671184' is the IMSI for ril_0, and that ril_1 is PIN-locked. It appears to me that NM may be trying contexts from other SIM directories it finds in /var/lib/ofono/.
So it looks you indeed have hit #1418077.
This is pretty obvious by looking in the attached nmlog file, and search for connection '/2081501026711 84/context1' . You'll see it get disabled at 18:41:24 after a bunch of failed attempts ( modem-no-carrier ). It gets successfully auto-activated again in +5m.
That said, I also see something else that concerns me.
If you look at the netlog, after '/2081501026711 84/context1' is disabled, you'll see NM try a 'context3', 'context5', and 'context1' again. The odd thing is that the related IMSI is not '208150102671184' it's '208103698221268'. Looking at network- test-session. log ( also attached ), you'll see that '208150102671184' is the IMSI for ril_0, and that ril_1 is PIN-locked. It appears to me that NM may be trying contexts from other SIM directories it finds in /var/lib/ofono/.