On 2017-02-06 11:28 AM, Aleksander Morgado wrote: >> At some point after adding the rule change, qmi-proxy seems to peg one >> of my cores basically forever. Is there a log I could look at to >> troubleshoot this? > Can you try to manually run the qmi-proxy? > > $ sudo systemctl stop ModemManager > $ sudo killall qmi-proxy > $ sudo /usr/lib/libqmi/qmi-proxy --no-exit --verbose > /tmp/qmi-proxy.log > 2>&1 & > $ sudo systemctl start ModemManager > > (and retry, log should have gone to /tmp/qmi-proxy.log)
Stopping ModemManager hung until I performed a -9 on qmi-proxy. So, after manually starting the proxy and ModemManager, I see the same "Failed to find primary AT port" message in syslog. Then I did a suspend/resume cycle and it eventually found the QMI port, then brought the network up. In this test, qmi-proxy did not deadlock. I rill try again right now. A. -- Adam Sherman <a...@sherman.ca>
qmi-proxy.log.bz2
Description: application/bzip
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
