| Summary: | ClientIdsExhausted on Quectel UC20G | ||
|---|---|---|---|
| Product: | ModemManager | Reporter: | samentu1 |
| Component: | general | Assignee: | ModemManager bug user <modemmanager> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 1.6 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
ModemManager --debug
logs captured by using: /usr/libexec/qmi-proxy --verbose --no-exit ModemManager debug log when qmi proxy was started with: /usr/libexec/qmi-proxy --verbose --no-exit |
||
Does this happen just after boot? Or does this happen e.g. after several suspend/resume cycles? Created attachment 135280 [details]
logs captured by using: /usr/libexec/qmi-proxy --verbose --no-exit
Created attachment 135281 [details]
ModemManager debug log when qmi proxy was started with: /usr/libexec/qmi-proxy --verbose --no-exit
Hi, this happens at boot time. Hi Aleksander, do I need to provide additional logs for helping debugging? Unfortunately none of the last logs provided show the ClientIdsExhausted issue... Anyway, I'm thinking that it may not be a bad idea to run a explicit "sync" operation any time the qmi-proxy starts, because that would flush any previously allocated and not released client id. The weird thing, though, is that this happens during boot time, so there shouldn't be any client id allocated previously. Yes, running qmi-network was done after MM was not able work just to see if it's something on MM's side or not. Sorry for the previous message (badly written) I had ran qmi-network after seeing that MM cannot manage the modem. The ClientIdsExhausted is showing up at boot, without ever running qmi-network before. What other logs could I supply? I have a different Quectel modem that is behaving in a similar fashion, so I can supply needed logs from this other one too. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/9. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 135263 [details] ModemManager --debug Hi, I am getting the following debug output on a Quectel UC20 modem, using ModemManager version 1.6.10 (see attachment debug.log)