Will modem inhibition truly release MBIM port ?

Aleksander Morgado aleksander at aleksander.es
Thu Sep 17 08:42:59 UTC 2020

Hey Edward,

>> You may have hitted a bug in the proxy! I don't think anyone ever
>> tried to send MBIM requests that wouldn't fit in a single fragment.
>> Could you send us a full mbim-proxy verbose log while this command is
>> being run? You'll need to run the proxy manually with --verbose
>> *before* MM is started.

Yes, I can see how only the first fragment has valid contents. The 2nd
fragment and following ones are invalid.

[17  九  2020, 08:22:52] -Error ** mbim_cid_get_printable: assertion
'cid > 0' failed
[17  九  2020, 08:22:52] [Debug] [/dev/cdc-wdm_pcie] Sent message (translated)...
<<<<<< Header:
<<<<<<   length      = 4096
<<<<<<   type        = command (0x00000003)
<<<<<<   transaction = 5
<<<<<< Fragment header:
<<<<<<   total   = 65
<<<<<<   current = 1
<<<<<< Contents:
<<<<<<   service = 'invalid' (00000000-0000-0000-0000-000000000000)
<<<<<<   cid     = '(null)' (0x00000000)
<<<<<<   type    = 'query' (0x00000000)

Would you be able to retest but using libmbim from git master, that
has improved debug logs?

At this point, and looking at your specific setup (with MBIM over PCIe
I'm assuming?) I don't know at which point the message splitting into
fragments is being done (if at your app level or at proxy level)


More information about the ModemManager-devel mailing list