Consultation about QMI CID Leaks

IOEE Jimmy Li (EXT) at
Thu Dec 30 01:45:53 UTC 2021

Hello Aleksander,

About qmicli commands, we are quite sure that we haven't run it.
And also, we don't run any other client neither. This issue happens when only MM restarted repeatedly.

-----Original Message-----
From: Aleksander Morgado <aleksander at>
Sent: Tuesday, December 28, 2021 6:00 PM
To: IOEE Jimmy Li (EXT) < at>
Cc: libqmi-devel at; ModemManager-devel at; Wang Qian (IOT) <wangqian at>; beizuo.liu at; IOEE Songting (EXT) <ioee.songting at>
Subject: Re: Consultation about QMI CID Leaks


> We have created the issue in Gitlab and uploaded all the logs that related.
> c9e8d521%7Caa06dce799d7403b8a080c5f50471e64%7C0%7C0%7C6377628241234828
> 39%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=G6krJsvRNvU8ucZVrBY8aBRnITado
> pT5J7YyzGaOlHI%3D&reserved=0
> Please contact us if there is still anything missing.
> Waiting for your kind reply. Thanks!

You missed to reply to my question before: can you confirm you're NOT running qmicli commands in addition to MM managing the modem? or are you running them?
If you're running custom qmicli commands you may be the one triggering the client ids exhausted. MM by itself doesn't (shouldn't) do that.


The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate, copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately.

More information about the ModemManager-devel mailing list