Hello,
do you still have this problem?
I was looking at your log and the USB serial changes introduced around
the time you hit this, and one of the suspicious patches seem to be
mine...
This looks very wrong:
[3.075097] usbcore: registered new interface driver usbserial
[3.075139] USB Serial support registered for generic
[3.262423] [drm] initialized overlay support
[3.276289] usbserial_generic 6-1:1.0: generic converter detected
[3.276592] usb 6-1: generic converter now attached to ttyUSB0
[3.276876] usb 6-1: generic converter now attached to ttyUSB1
[3.277137] usb 6-1: generic converter now attached to ttyUSB2
[3.277178] usbcore: registered new interface driver usbserial_generic
[3.277185] usbserial: USB Serial Driver core
[3.279835] USB Serial support registered for Sierra USB modem
[3.279902] usbcore: registered new interface driver sierra
[3.279907] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems
Your modem should not match the generic converter. It should match
the sierra driver. But as you can see, the generic driver has already
bound to the three serial ports by the time the sierra driver is loaded,
so this won't happen.
Do you by any chance set the vendor and product usbserial
parameters manually somewhere? That would explain the above log. Look
for any usbserial entry in /etc/modules /etc/modprobe.d/*.conf or local
init scripts. These are unnecessary and may cause problems.
But I still do not understand how this can prevent the modem from
working. AFAICS it should still work, only at the slower generic serial
driver speed. The change I introdcued in v3.2.20 should only affect
probing, and only the case where a device could end up being
unintentionally bound to the generic driver.
Bjørn
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ppw34kw8@nemi.mork.no
