EM9190 randomly dial fail

Mon Apr 26 08:56:13 UTC 2021

Hi Aleksander,

Thanks your response. see below updates.

Are you running that command as part of a script or something? If you run mbimcli without using the --no-close and --no-open options; carefully, I assume you could get in such a situation quickly.
My test unit can install two EM9190 modems, and my dial command steps for each EM9190 as below.
# PROXY=yes mbim-network /dev/cdc-wdmx start
# busybox udhcpc -i wwanx

If I reboot system, the two modems sometimes can work, or one can work or both can't work. see below.
# PROXY=yes mbim-network /dev/cdc-wdm1 start
APN:
APN user:
APN password:
APN user:
mbim-proxy: yes
Profile at '/etc/mbim-network.conf' not found...
Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm1 --query-subscriber-ready-status --no-close --device-open-proxy'...
error: couldn't open the MbimDevice: Transaction timed out

Querying registration state 'mbimcli -d /dev/cdc-wdm1 --query-registration-state --no-open= --no-close --device-open-proxy'...
error: invalid transaction ID specified:

Attaching to packet service with 'mbimcli -d /dev/cdc-wdm1 --attach-packet-service --no-open= --no-close --device-open-proxy'...
error: invalid transaction ID specified:
Starting network with 'mbimcli -d /dev/cdc-wdm1 --connect=apn='' --no-open= --no-close --device-open-proxy'...
error: invalid transaction ID specified:
Network start failed

# PROXY=yes mbim-network /dev/cdc-wdm0 start
APN:
APN user:
APN password:
APN user:
mbim-proxy: yes
Profile at '/etc/mbim-network.conf' not found...
Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy'...
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '460042240808109' SIM ICCID: '89860402101703508108' Ready info: 'none' Telephone numbers: (0) 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '4'
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 4)
Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy'...
[/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '46000' Provider name: 'CMCC' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '6'
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 6)
Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy'...
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 8)
Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=8 --no-close --device-open-proxy'...
Network started successfully
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 11)

if I continue to run command manually without "--no-close --device-open-proxy", also encounter the same error log. see below.
# mbimcli -d /dev/cdc-wdm1 --query-subscriber-ready-status
error: couldn't open the MbimDevice: Failure

# mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status
error: operation failed: Transaction timed out
error: couldn't close device: Transaction timed out

the result of command "lsof" as below.
[10.12.32.138]# lsof | grep cdc
2353 /usr/lib64/mbim-proxy /dev/cdc-wdm0

Have you tried to run ALL your mbimcli commands with the '-p' option (to run through the proxy). When running with the proxy, it's the proxy itself the one who keeps track of the open/closed MBIM session
Yes, I run all mbim commands with "-p"

And another question, when you reboot your system, is the EM9190 also power cycled? or is it kept powered? Maybe the MBIM session is kept open in the device while the host thinks it should be closed?

when reboot system, the mother board and hub both power off ,then power on

--

Best Regards,
Dai,Lijin

At 2021-04-26 16:24:54, "dailijin" <dailijin126 at 126.com> wrote:
>Hi Aleksander,<br/><br/>Thanks your response.  see below updates.<br/><br/>> Are you running that command as part of a script or something? If you<br/>> run mbimcli without using the --no-close and --no-open options<br/>> carefully, I assume you could get in such a situation quickly.<br/>My test unit can install two EM9190 modems, and my dial command steps for each EM9190 as below.<br/><br/># PROXY=yes mbim-network /dev/cdc-wdmx start<br/># busybox udhcpc -i wwanx<br/><br/>If I reboot system, the two modems sometimes can work, or one can work or both can't work. see below.<br/><br/># PROXY=yes  mbim-network /dev/cdc-wdm1 start  <br/>    APN: <br/>    APN user: <br/>    APN password: <br/>    APN user: <br/>    mbim-proxy: yes<br/>Profile at '/etc/mbim-network.conf' not found...<br/>Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm1 --query-subscriber-ready-status --no-close --device-open-proxy'...<br/>error: couldn't open the MbimDevice: Transaction timed out<br/><br/>Querying registration state 'mbimcli -d /dev/cdc-wdm1 --query-registration-state --no-open= --no-close --device-open-proxy'...<br/>error: invalid transaction ID specified: <br/><br/>Attaching to packet service with 'mbimcli -d /dev/cdc-wdm1 --attach-packet-service --no-open= --no-close --device-open-proxy'...<br/>error: invalid transaction ID specified: <br/>Starting network with 'mbimcli -d /dev/cdc-wdm1 --connect=apn='' --no-open= --no-close --device-open-proxy'...<br/>error: invalid transaction ID specified: <br/>Network start failed<br/><br/># PROXY=yes mbim-network /dev/cdc-wdm0 start                                                                           <br/>    APN: <br/>    APN user: <br/>    APN password: <br/>    APN user: <br/>    mbim-proxy: yes<br/>Profile at '/etc/mbim-network.conf' not found...<br/>Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy'...<br/>[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '460042240808109' SIM ICCID: '89860402101703508108' Ready info: 'none' Telephone numbers: (0) 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '4'<br/>Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 4)<br/>Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy'...<br/>[/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '46000' Provider name: 'CMCC' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '6'<br/>Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 6)<br/>Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy'...<br/>Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 8)<br/>Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=8 --no-close --device-open-proxy'...<br/>Network started successfully<br/>Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 11)<br/><br/>if I continue to run command manually without "--no-close --device-open-proxy",  also encounter the same error log. see below.<br/># mbimcli -d /dev/cdc-wdm1 --query-subscriber-ready-status                                                             <br/>error: couldn't open the MbimDevice: Failure<br/># mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status                                                             <br/>error: operation failed: Transaction timed out<br/><br/>the result of command "lsof" as below.<br/># lsof | grep cdc-wdm                                                                                                  <br/>2353	/usr/lib64/mbim-proxy	/dev/cdc-wdm0<br/><br/><br/>>Have you tried to run ALL your mbimcli commands with the '-p' option<br/>>(to run through the proxy). When running with the proxy, it's the<br/>>proxy itself the one who keeps track of the open/closed MBIM session<br/>Yes, I run all mbim commands with "-p"<br/><br/>>And another question, when you reboot your system, is the EM9190 also<br/>>power cycled? or is it kept powered? Maybe the MBIM session is kept<br/>>open in the device while the host thinks it should be closed?<br/>when reboot system, the mother board and  hub both power off ,then power on
>At 2021-04-26 15:48:48, "Aleksander Morgado" <aleksander at aleksander.es> wrote:
>>Hey,
>>
>>> I am testing Sierra 5G modem EM9190. my kernel  version is V4.4.13 and use the default driver cdc_mbim.ko.  the modem randomly can't dial success after I reboot system.
>>>
>>> I checked AT command 'AT!GSTATUS' and confirm the modem can connect cell station successfully, but mbim-network always execute fail.  the error log is "error: couldn't open the MbimDevice: Failure".
>>>
>>> I am using libmbim version  1.14.0. do you any guys encounter the same issue?
>>>
>>> [10.12.32.138]# mbimcli -d /dev/cdc-wdm3 --query-connection-state -v
>>> [22 Apr 2021, 08:41:38] [Debug] opening device...
>>> [22 Apr 2021, 08:41:38] [Debug] [/dev/cdc-wdm3] Queried max control message size: 4096
>>> [22 Apr 2021, 08:41:38] [Debug] [/dev/cdc-wdm3] Sent message...
>>> <<<<<< RAW:
>>> <<<<<<   length = 16
>>> <<<<<<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
>>>
>>> [22 Apr 2021, 08:41:38] [Debug] [/dev/cdc-wdm3] Sent message (translated)...
>>> <<<<<< Header:
>>> <<<<<<   length      = 16
>>> <<<<<<   type        = open (0x00000001)
>>> <<<<<<   transaction = 1
>>> <<<<<< Contents:
>>> <<<<<<   max control transfer = 4096
>>>
>>> [22 Apr 2021, 08:41:40] [Debug] [/dev/cdc-wdm3] Received message...
>>> >>>>>> RAW:
>>> >>>>>>   length = 16
>>> >>>>>>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:02:00:00:00
>>>
>>> [22 Apr 2021, 08:41:40] [Debug] getting open done result failed: closed
>>> error: couldn't open the MbimDevice: Failure
>>>
>>
>>Are you running that command as part of a script or something? If you
>>run mbimcli without using the --no-close and --no-open options
>>carefully, I assume you could get in such a situation quickly.
>>
>>Have you tried to run ALL your mbimcli commands with the '-p' option
>>(to run through the proxy). When running with the proxy, it's the
>>proxy itself the one who keeps track of the open/closed MBIM session.
>>
>>And another question, when you reboot your system, is the EM9190 also
>>power cycled? or is it kept powered? Maybe the MBIM session is kept
>>open in the device while the host thinks it should be closed?
>>
>>You'll need to investigate a bit more following those hints :) Please
>>let us know what you discover.
>>
>>-- 
>>Aleksander
>>https://aleksander.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libmbim-devel/attachments/20210426/89e0f640/attachment-0001.htm>