dlink dwm221-B1 failed regression test - time out
Thomas Schäfer
tschaefer at t-online.de
Sat Apr 15 20:12:25 UTC 2017
Am Freitag, 14. April 2017, 23:56:30 schrieb Aleksander Morgado:
>
> Could you try getting debug logs as generated by the qmi-proxy?
> There's are some "broken pipe" errors in the MM log that I don't like,
> maybe the proxy is segfaulting or something. Steps to get the logs
> would be:
>
> $ sudo systemctl stop ModemManager
> $ sudo killall -9 qmi-proxy
> $ sudo /usr/libexec/qmi-proxy --verbose --no-exit > /tmp/qmi-proxy.log 2>&1
> & $ sudo systemctl start ModemManager
>
> Hopefull you'll then get the qmi proxy logs in that file, let's see if
> we see something there.
There is something.
The log file is attached.
Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qmi-proxy.log.xz
Type: application/x-xz
Size: 4072 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170415/59b9db74/attachment.xz>
More information about the libqmi-devel
mailing list