On Wed, 2025-07-16 at 17:35 +0200, Armand Daussà wrote: > Hi, > > We’ve encountered an issue with modem disconnections and have > reviewed the ModemManager logs to better understand the behavior. > What we observed is that after a disconnection, ModemManager attempts > to reconnect but then shuts down and does not attempt to reconnect > again. It only resumes connection attempts after the operating system > is rebooted. > > In situations where the modem experiences issues and cannot establish > a connection, ModemManager appears to stop trying entirely until the > next system reboot. Eventually, after a reboot, ModemManager is able > to successfully initialize the modem and re-establish a connection. > > Could you please confirm if this is the expected behavior? If not, is > there a recommended way to ensure that ModemManager continues trying > to reconnect without requiring a system reboot?
ModemManager itself does not actually start/stop the data connection. That's typically done by a connection manager, like NetworkManager, distro network scripts, or custom scripting. In the NetworkManager case, it will stop asking MM to reconnect after a configurable number of failures. It will then start a timer and when the timer expires, retry until the configurable number of failures. Repeat. Do you know what connection manager you're using to drive ModemManager? If we can figure that out we can nail down the reconnect behavior. > > Is it something fixed in more recent releases? > > Key timestamps: > 16:37:24 -> Modem sends '<CR><LF>+SIMCARD: NOT AVAILABLE<CR><LF>' > Five OS Reboots are performed > 19:19:21 -> Modem manager starts following last reboot and a > successful initialization is completed > > Logs are attached. I do notice: Jul 14 16:37:24 fonts2 ModemManager[498]: <info> [1752503844.286189] [modem0/bearer1] bearer call end reason (1): 'generic-unspecified' Jul 14 16:37:24 fonts2 ModemManager[498]: <info> [1752503844.286265] [modem0/bearer1] bearer verbose call end reason (2,218): [internal] mmgdsi-card-event The call here gets terminated by mmgdsi-card-event which I think is *actually* GSDI = Generic Sim Driver Interface card event. Which correlates to the +SIMCARD message and indicates that the SIM card or the modem's SIM interface decided to hiccup and that terminated the call. I'm not surprised things are broken until a reboot, but if this is a physical SIM card you might try removing and re-inserting the SIM and see if that makes things work more quickly. In any case, if you're able to determine what connection manager you use, then we can figure out the reconnect behavior. Dan > > Thanks in advance! > > System info: > OS: > Linux fonts1 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST > 2023 aarch64 > > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > > > > > Hardware > > manufacturer: QUALCOMM INCORPORATED > > model: 0 (doesn't show but its a SIMCOM S2-107EQ) > > firmware revision: LE11B12SIM7600M22 > > carrier config: ROW_Gen_NonVoLTE > > carrier config revision: 05010813 > > > > h/w revision: 10000 > > supported: gsm-umts, lte > > current: gsm-umts, lte > > > > > ModemManager version > 1.14.12
