Odd MM Bearer behavior
Christopher Penney
mrpher at gmail.com
Wed May 26 02:06:30 UTC 2021
Hi Aleksander, hoping to ask another favor on this same thread. You helped
me fix profile [1] which worked perfectly (thanks again), but the device
recently lost connection and tried to re-establish after reset where it
seems to be trying to connect to profile [4] and recycling through the same
bearer increase loop. I say this because in mmcli -m 0, the access tech:
umts which looks like it was my profile [4], not profile [1]. Is there a
way to force it to connect to a specific profile at boot? If not, how do
we manually force to connect to the correct profile? Logs below.
Thanks!
=============================================================
Welcome to balenaOS
=============================================================
root at 325da06:~# mmcli -m 0
-----------------------------------
General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: [REDACTED]
-----------------------------------
Hardware | manufacturer: QUALCOMM INCORPORATED
| model: QUECTEL Mobile Broadband Module
| firmware revision: EG25GGBR07A08M2G
| carrier config: Commercial-TMO_VoLTE
| carrier config revision: 05010505
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: [REDACTED]
-----------------------------------
System | device:
/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
| drivers: option1, qmi_wwan
| plugin: quectel
| primary port: cdc-wdm0
| ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm),
ttyUSB2 (at), wwan0 (net),
| ttyUSB1 (gps), ttyUSB3 (at)
-----------------------------------
Numbers | own: 15[REDACTED]18
-----------------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2
(10), sim-puk2 (10)
| state: connecting
| power state: on
| access tech: umts
| signal quality: 49% (recent)
-----------------------------------
Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: 2g, 3g, 4g; preferred: 4g
-----------------------------------
Bands | supported: egsm, dcs, pcs, g850, utran-1,
utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2,
eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12,
eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26,
eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19
| current: egsm, dcs, pcs, g850, utran-1,
utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2,
eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12,
eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26,
eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19
-----------------------------------
IP | supported: ipv4, ipv6, ipv4v6
-----------------------------------
3GPP | imei: [REDACTED]
| operator id: 310260
| operator name: T-Mobile
| registration: home
-----------------------------------
3GPP EPS | ue mode of operation: csps-1
-----------------------------------
SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
-----------------------------------
Bearer | dbus path:
/org/freedesktop/ModemManager1/Bearer/3
root at 325da06:~# journalctl -u ModemManager
May 26 01:59:00 325da06 ModemManager[1401]: [modem0/bearer17] connection
attempt #1 failed: QMI protocol error (14): 'CallFailed'
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] state changed
(connecting -> registered)
May 26 01:59:00 325da06 ModemManager[1401]: [modem0/bearer17] connection #1
finished: duration 0s, tx: 0 bytes, rx :0 bytes
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect
started...
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state
(4/8): wait to get fully enabled
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state
(5/8): register
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state
(6/8): bearer
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state
(7/8): connect
May 26 01:59:00 325da06 ModemManager[1401]: [modem0] state changed
(registered -> connecting)
May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] couldn't
start network: QMI protocol error (14): 'CallFailed'
May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] call end
reason (1016): gsm-wcdma-activation-reject
May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] verbose call
end reason (6,31): [3gpp] activation-reject
May 26 01:59:11 325da06 ModemManager[1401]: [base-manager] couldn't check
support for device '/sys/devices/platform/soc/3f300000.mmcnr/mmc_hos>
May 26 01:59:11 325da06 ModemManager[1401]: [base-manager] couldn't check
support for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/>
May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] couldn't
start network: QMI protocol error (14): 'CallFailed'
May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] call end
reason (1016): gsm-wcdma-activation-reject
May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] verbose call
end reason (6,31): [3gpp] activation-reject
May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] connection
attempt #1 failed: QMI protocol error (14): 'CallFailed'
On Tue, May 18, 2021 at 8:36 AM Christopher Penney <mrpher at gmail.com> wrote:
> Makes sense. I guess I could always automate with a boot script.
> Thanks again.
>
> On Tue, May 18, 2021 at 8:19 AM Aleksander Morgado <
> aleksander at aleksander.es> wrote:
>
>> Hey,
>>
>> On Tue, May 18, 2021 at 12:47 PM Christopher Penney <mrpher at gmail.com>
>> wrote:
>> >
>> > Wow, it worked! Thank you VERY VERY much. Turns out the problem was
>> exactly that; the default profile was incompatible with IoTDataWorks
>> default APN.
>> > You really saved the day (week, months really) thanks again.
>> >
>>
>> Glad it worked!
>>
>> > I'll let the Balena team know about the default versions and the fix in
>> case others run into the same problem.
>> >
>> > Meantime, one more favor to ask - is there a programmatic way to clear
>> that default profile at boot rather than have to do it manually on each new
>> device we provision?
>> >
>>
>> No, there is no such thing right now. ModemManager won't do any
>> "automatic" configuration of this kind, if there are profile changes
>> to be done, they should be requested by the user.
>>
>> --
>> Aleksander
>> https://aleksander.es
>>
> --
> Sent from my phone pardon the typos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20210525/03de1f9c/attachment-0001.htm>
More information about the ModemManager-devel
mailing list