Modem kernel driver changes from cdc_mbim to qmi_wwan after suspend/resume?

[Amol Lad]

Can we see the output of AT!USBCOMP? AT command before and after the issue?

root at OpenWrt:/# mmcli -m 0 --command=AT!ENTERCND=\"A710\"
response: ''
root at OpenWrt:/# mmcli -m 0 --command=AT!USBCOMP?
response: 'Config Index: 1
Config Type:  3 (Generic)
Interface bitmask: 0000100D (diag,nmea,modem,mbim) '
root at OpenWrt:/#


The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).-----Original Message-----
From: ModemManager-devel <modemmanager-devel-bounces at lists.freedesktop.org> On Behalf Of Aleksander Morgado
Sent: Thursday, 19 December 2019 3:36 PM
To: Bjørn Mork <bjorn at mork.no>
Cc: ModemManager (development) <modemmanager-devel at lists.freedesktop.org>
Subject: Modem kernel driver changes from cdc_mbim to qmi_wwan after suspend/resume?

Hey Bjørn & all,

I wonder if you have any idea why this issue is happening?
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/165#note_368404

We can see how the kernel driver reported as managing the device that owns the cdc-wdm port changes from cdc_mbim (original one after boot) to qmi_wwan (after a suspend/resume cycle). This makes ModemManager attempt QMI probing instead of MBIM probing on the port, and that fails, so the modem is no longer used after the suspend/resume cycle.

Any hint?

--
Aleksander
https://aleksander.es
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel