EG25G with latest firmware GBR07A08 loose connection and never connect again

Hello,

I saw the following problem on two independent modems EG25G (miniPCIe) in the last three days. One was located on US east coast and the second is located in Germany. The firmware was updated about two weeks ago. The modems were connected via LTE. It is normal that the modem can loose the connection and reconnects less or more minutes later. But in this case the modems didn’t reconnected. The first modem, located in US and installed in an embedded system (gateway) with embedded Linux (kernel 5.4) toggled permanently between registered and connecting, see log

Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Simple connect started…
Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Simple connect state (4/8): Wait to get fully enabled
Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Simple connect state (5/8): Register
Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Simple connect state (6/8): Bearer
Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Simple connect state (7/8): Connect
Sep 01 12:11:03 mcg-gw-3170000108 ModemManager[227]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: call end reason (3): ‘generic-no-service’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: verbose call end reason (3,2007): [cm] (null)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: call end reason (3): ‘generic-no-service’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: verbose call end reason (3,2007): [cm] (null)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Simple connect started…
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Simple connect state (4/8): Wait to get fully enabled
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Simple connect state (5/8): Register
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Simple connect state (6/8): Bearer
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Simple connect state (7/8): Connect
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: call end reason (3): ‘generic-no-service’
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: verbose call end reason (3,2007): [cm] (null)
Sep 01 12:11:04 mcg-gw-3170000108 ModemManager[227]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)

and the second modem, installed on a desktop system with latest Linux Mint as an external USB device toggled permanently between registered and connecting, connected sometime for a short time and toggled back to registered, see following log

Sep 02 08:05:01 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
Sep 02 08:05:01 05-chqu-pc ModemManager[1142]: Simple connect state (8/8): All done
Sep 02 08:06:11 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (roaming -> registering)
Sep 02 08:06:11 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: bearer call end reason (3): ‘generic-no-service’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: bearer verbose call end reason (3,1028): [cm] (null)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> registered)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Reloading stats failed: Couldn’t get packet statistics: QMI protocol error (15): ‘OutOfCall’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect started…
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (4/8): Wait to get fully enabled
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (5/8): Register
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (6/8): Bearer
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (7/8): Connect
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: call end reason (3): ‘generic-no-service’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: verbose call end reason (3,2001): [cm] no-service
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect started…
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (4/8): Wait to get fully enabled
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (5/8): Register
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (6/8): Bearer
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (7/8): Connect
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: call end reason (3): ‘generic-no-service’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: verbose call end reason (3,2001): [cm] no-service
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect started…
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (4/8): Wait to get fully enabled
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (5/8): Register
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (6/8): Bearer
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Simple connect state (7/8): Connect
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: call end reason (3): ‘generic-no-service’
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: verbose call end reason (3,2001): [cm] no-service
Sep 03 01:09:32 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect started…
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect state (4/8): Wait to get fully enabled
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect state (5/8): Register
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect state (6/8): Bearer
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect state (7/8): Connect
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: QMI IPv4 Settings:
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Address: 10.161.117.39/28
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Gateway: 10.161.117.40
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: DNS #1: 192.168.10.110
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: DNS #2: 194.51.3.56
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: MTU: 1500
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
Sep 03 01:14:33 05-chqu-pc ModemManager[1142]: Simple connect state (8/8): All done
Sep 03 01:15:27 05-chqu-pc ModemManager[1142]: bearer call end reason (1041): ‘(null)’
Sep 03 01:15:27 05-chqu-pc ModemManager[1142]: bearer verbose call end reason (3,1008): [cm] ms-identity-not-derived-by-the-network
Sep 03 01:15:27 05-chqu-pc ModemManager[1142]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> registered)
Sep 03 01:15:27 05-chqu-pc ModemManager[1142]: Simple connect started…

In both cases it was like a dead lock. Only a restart of the whole embedded system or power off / on of the external modem solved the problem. At the same time four other devices with the same modem worked well and were permanent online.

Regards
Christian Quass

Dear Christian,
Thanks for your inquiry in Quectel forum.
About your issue, it is may need to catch module debug log to confirm the module status. As you know that it should have no such issue except the network signal is abnormal. You may check it when meet such issue. And you also can try to set AT+CFUN=0, then AT+CFUN=1 to check whether it can restore without restart the module. Thanks!

I’m not sure if you mean the ModemManager debug log or if the Quectel module has its own debug log. If the module has a separate debug log it would be nice if you can give me a tip, how to get it.
Since Yesterday I have the same issue in Shanghai. There are two systems in the same office. The module in the embedded system works fine and the module as external USB modem, connected on a Intel NUC with latest Linux Mint has the same issue since Yesterday about 11:20 utc (13:20 inside the log file), beginning after a restart. I resetted the modem with ‘mmcli -m 0 -r’, powered it off via mmcli command, rebooted the host system, the issue is permanent. I don’t know if the modem is really powered off during host restart, it seems so, about one second during restart the activity indication is off, normally it is permanent on or blinking, but I’m not sure.
I have configured debug mode for modem manager and shared the journal output. It starts with normal operation yesterday and the latest entries are debug entries.
I’ll uploadModemManager_LinuxMint_Shanghai_2020-09-10_01.pdf (1.3 MB) the logfile ‘ModemManager_LinuxMint_Shanghai_2020-09-10.log’.
Thanks in advance

1 Like

Hi! Were you able to solve the problem?