RM520N-GL Modem Manager marks invalid

IoT Modules 5G Module
1

Hello,
We are using RM520N-GL modems in Debian 12, via USB3. After some time of good operation, the ModemManager can’t contact the modem via the QMI port and marks it as invalid, thereby ending the internet connection. We have seen this happen as quickly as 10 minutes after boot, and other time it first happens after ~3 Days.

host@hostname:~$ sudo journalctl -u ModemManager -b -1 | grep "modem"
Dec 01 13:29:02 hostname ModemManager[309]: <info>  [device /sys/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:08.0/0000:08:00.0/usb7/7-1] creating modem with plugin 'quectel' and '6' ports
Dec 01 13:29:02 hostname ModemManager[309]: <info>  [base-manager] modem for device '/sys/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:08.0/0000:08:00.0/usb7/7-1' successfully created
Dec 01 13:29:05 hostname ModemManager[309]: <warn>  [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""'
Dec 01 13:29:05 hostname ModemManager[309]: <warn>  [modem0] couldn't load list of own numbers: Couldn't get MSISDN: QMI protocol error (16): 'NotProvisioned'
Dec 01 13:29:16 hostname ModemManager[309]: <warn>  [modem0] couldn't load supported assistance data types: Failed to receive indication with the predicted orbits data source
Dec 01 13:29:16 hostname ModemManager[309]: <info>  [modem0] state changed (unknown -> disabled)
Dec 01 13:29:16 hostname ModemManager[309]: <info>  [modem0] state changed (disabled -> enabling)
Dec 01 13:29:16 hostname ModemManager[309]: <info>  [modem0] simple connect started...
Dec 01 13:29:16 hostname ModemManager[309]: <info>  [modem0] simple connect state (4/10): wait to get fully enabled
Dec 01 13:29:16 hostname ModemManager[309]: <info>  [modem0] power state updated: on
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] state changed (enabling -> enabled)
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] simple connect state (5/10): wait after enabled
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] 3GPP registration state changed (unknown -> registering)
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] 3GPP registration state changed (registering -> home)
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] state changed (enabled -> registered)
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] simple connect state (6/10): register
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] simple connect state (7/10): wait to get packet service state attached
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] simple connect state (8/10): bearer
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] simple connect state (9/10): connect
Dec 01 13:29:18 hostname ModemManager[309]: <info>  [modem0] state changed (registered -> connecting)
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1] QMI IPv4 Settings:
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1]     address: 10.193.181.17/30
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1]     gateway: 10.193.181.18
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1]     DNS #1: 193.247.204.1
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1]     DNS #2: 193.5.23.1
Dec 01 13:29:19 hostname ModemManager[309]: <info>  [modem0/bearer1]        MTU: 1280
Dec 01 13:29:20 hostname ModemManager[309]: <info>  [modem0/bearer1] reloading stats is supported by the device
Dec 01 13:29:20 hostname ModemManager[309]: <info>  [modem0] state changed (connecting -> connected)
Dec 01 13:29:20 hostname ModemManager[309]: <info>  [modem0] simple connect state (10/10): all done
Feb 13 11:32:22 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 2 consecutive times
Feb 13 11:32:23 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 2 consecutive times
Feb 13 11:32:24 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 3 consecutive times
Feb 13 11:32:24 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 4 consecutive times
Feb 13 11:32:24 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 5 consecutive times
Feb 13 11:32:25 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 6 consecutive times
Feb 13 11:32:25 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 7 consecutive times
Feb 13 11:32:26 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 2 consecutive times
Feb 13 11:32:27 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 3 consecutive times
Feb 13 11:32:27 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 4 consecutive times
Feb 13 11:32:27 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 5 consecutive times
Feb 13 11:32:28 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 6 consecutive times
Feb 13 11:32:28 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 7 consecutive times
Feb 13 11:32:28 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 8 consecutive times
Feb 13 11:32:29 hostname ModemManager[309]: <warn>  [modem0] port cdc-wdm0 timed out 9 consecutive times
Feb 13 11:32:29 hostname ModemManager[309]: <error> [modem0] port cdc-wdm0 timed out 10 consecutive times, marking modem as invalid
Feb 13 11:32:29 hostname ModemManager[309]: <error> [modem0] port cdc-wdm0 timed out 11 consecutive times, marking modem as invalid
Feb 13 11:32:29 hostname ModemManager[309]: <error> [modem0] port cdc-wdm0 timed out 12 consecutive https://forums.quectel.com/c/technical-subjects/17times, marking modem as invalid
Feb 13 11:32:29 hostname ModemManager[309]: <warn>  [modem0/bearer1] reloading stats failed: QMI operation failed: Transaction timed out

We have experimented with various firmware versions.

  • For the latest R03 firmware ( RM520NGLAAR03A04M4G_01.204.01.204) we did not yet observe it, but it might come up again.
  • For the latest R01 firmware ( RM520NGLAAR01A08M4G_01.206.01.206) we saw the QMI operation failed: Transaction timed out issue. (this firmware has a newer release date than the R03 firmware.)

Is this a known issue? Is it related to firmware or sim card used? How can we ensure that this wont occur again? What is the difference between R03 and R01 firmware?

2

Is it the native driver qmi_wwan?

3

I got RM520-NL IN MY SYSTEM .IAM USING RM520NGLAAR03A03M4G_01.201.01.201 THIS ALONG WITH QFLASH 7.0.is there any update to RM520NGLAAR03A03M4G_01.201.01.201 this version .please give me details if there is any update version which i can use along with it

4

No need to upgrade.
Still the latest firmware.

5

will there be any difference if i use Qflash latest version .

6

Does this answer your question:

host@hostname:~$ lsmod | grep qmi_wwan
qmi_wwan               49152  0
cdc_wdm                49152  2 qmi_wwan

host@hostname:~$ sudo dmesg | grep -i qmi
[   35.544093] usbcore: registered new interface driver qmi_wwan
[   41.331774] qmi_wwan 7-1:1.4: cdc-wdm0: USB WDM device
[   41.338670] qmi_wwan 7-1:1.4 wwan0: register 'qmi_wwan' at usb-0000:08:00.0-1, WWAN/QMI device, 7e:d1:23:14:**:**
[   42.298888] qmi_wwan 7-1:1.4 wwan0: unregister 'qmi_wwan' usb-0000:08:00.0-1, WWAN/QMI device
[   44.306617] qmi_wwan 7-1:1.4: cdc-wdm0: USB WDM device
[   44.312394] qmi_wwan 7-1:1.4 wwan0: register 'qmi_wwan' at usb-0000:08:00.0-1, WWAN/QMI device, 8e:f3:a6:44:**:**

host@hostname:~$ uname -r
6.6.74-v8-16k+

host@hostname:~$ mmcli --version
mmcli 1.20.4
Copyright (2011 - 2022) Aleksander Morgado
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
7

We don’t know which QMI message is not supported or marked as invalid.