error: operation failed: Transaction timed out
I get very frequent Transation timeouts when using libqmi. I've mostly been using the default libqmi-utils package on Ubuntu 12.04: $ sudo dpkg -l | grep -i qmi-utils libqmi-utils 1.4.0-1 amd64 I have also tried the latest github version, which I built and installed from source. I still get transation timeout errors with that version also. The modem I am using is a Sierra Wireless MC7710 based USB LTE modem $ lsusb | grep 68a2 Bus 001 Device 003: ID 1199:68a2 Sierra Wireless, Inc. I am able to bring up a network connection, but the qmicli commands fail frequently with timeouts. ----8<-----------------------8<-------- sudo qmicli -d /dev/cdc-wdm0 --wds-start-network= --client-no-release-cid sudo dhclient -d -4 wwan0 sudo dhclient -r wwan0 sudo qmicli -d /dev/cdc-wdm0 --wds-stop-network=<id-as-previous> --client-cid=<cid-as-previous> I also want to monitor status which I have been using the following: sudo qmicli -d /dev/cdc-wdm0 --nas-noop --client-no-release-cid sudo qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength --client-no-release-cid --client-cid=<assigned-cid> sudo qmicli -d /dev/cdc-wdm0 --nas-noop --client-cid <assigned-cid> ----8<-----------------------8<-------- Sometimes the commands above work, but frequently the fail with Transaction timeout messages. I don't have any other qmicli instances running. I don't know if this is a bug, or perhaps I am misusing qmicli?
(In reply to Eddy Higgins from comment #1) > I get very frequent Transation timeouts when using libqmi. I've mostly been > using the default libqmi-utils package on Ubuntu 12.04: > > $ sudo dpkg -l | grep -i qmi-utils > libqmi-utils 1.4.0-1 amd64 > > I have also tried the latest github version, which I built and installed > from source. I still get transation timeout errors with that version also. > > The modem I am using is a Sierra Wireless MC7710 based USB LTE modem > $ lsusb | grep 68a2 > Bus 001 Device 003: ID 1199:68a2 Sierra Wireless, Inc. > > I am able to bring up a network connection, but the qmicli commands fail > frequently with timeouts. > > ----8<-----------------------8<-------- > sudo qmicli -d /dev/cdc-wdm0 --wds-start-network= --client-no-release-cid > sudo dhclient -d -4 wwan0 > > sudo dhclient -r wwan0 > sudo qmicli -d /dev/cdc-wdm0 --wds-stop-network=<id-as-previous> > --client-cid=<cid-as-previous> > > I also want to monitor status which I have been using the following: > sudo qmicli -d /dev/cdc-wdm0 --nas-noop --client-no-release-cid > sudo qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength > --client-no-release-cid --client-cid=<assigned-cid> > > sudo qmicli -d /dev/cdc-wdm0 --nas-noop --client-cid <assigned-cid> > ----8<-----------------------8<-------- > Sometimes the commands above work, but frequently the fail with Transaction > timeout messages. > > I don't have any other qmicli instances running. > > I don't know if this is a bug, or perhaps I am misusing qmicli? Do you also have ModemManager installed? In libqmi < 1.8 and ModemManager < 1.2, you wouldn't be able to use the cdc-wdm port properly if ModemManager was using it; i.e. only one process would be able to use it without errors. If you also have ModemManager installed in the system I'd suggest you try with ModemManager 1.4 (latest stable) and libqmi 1.10.x (latest stable). Once you have those installed, make sure to always pass "--proxy" or just "-p" to the qmicli commands, so that they all go through the new qmi-proxy infrastructure. More info here: http://sigquit.wordpress.com/2013/09/13/sharing-a-qmi-port-between-processes/ If you cannot upgrade versions for whatever reasons; just make sure ModemManager is not running while you try the qmicli commands. I'll set as NEEDINFO until reporter confirms whether the newer versions + proxy solved the issues.
Closing as no further info has been provided. Anyway, this Transaction timed out issue is very common when multiple qmicli commands are running at the same time without the qmi-proxy, as only one such qmicli is able to receive the responses.
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.