> On Sun, 2016-01-03 at 20:50 +0100, Bjørn Mork wrote:
>
>> But like you, I cannot find the commit supposed to fix this. There is
>> no such commit in net, net-next, usb or usb-next AFAICS. And I can't
>> find any other relevant commit after the one introducing this bug
>> either. Did you
> On Sat, 2016-01-02 at 06:11 +0300, Vasily Galkin wrote:
>
>> I reverted 823bd3433424aa959499e6fd8f2da842430a8d42 and recompiled cdc_ether
>> module for debian's 4.4rc6.
>> Device begin working normally as usual, no any Oopses or problems.
>>
>> At
storage with drivers, and then is swithced to actual networking
device 1076:8002.
I\m attaching lsusb -v output for both modes.
> On Thu, 2015-12-31 at 07:22 +0300, Vasily Galkin wrote:
>
>> After switching from 4.3 to 4.4rc-s plugging device ID 1076:8002 GCT
>> Semiconductor, In
rm *rc1*dmesgAfter switching from 4.3 to 4.4rc-s plugging device ID 1076:8002
GCT Semiconductor, Inc. LU150 LTE Modem [Yota LU150] causes kernel Oops.
The Oops is always reproducible when this device is plugged or system is booted
with it.
Oops reproduced with debian's 4.4.rc6 and vanilla
