Re: rndis/cdc_ether usb device causing Oops in 4.4rc1+ with NULL dereference

2016-01-03 Thread Oliver Neukum
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 forget to

Re: rndis/cdc_ether usb device causing Oops in 4.4rc1+ with NULL dereference

2016-01-03 Thread Bjørn Mork
Vasily Galkin writes: > I reverted 823bd3433424aa959499e6fd8f2da842430a8d42 and recompiled cdc_ether > module for debian's 4.4rc6. > Device begin working normally as usual, no any Oopses or problems. > > Attaching lsusb output for this kernel. [..] > Interface

Trouble posting from gmail, was Re: rndis/cdc_ether usb device causing Oops in 4.4rc1+ with NULL dereference

2016-01-02 Thread Peter Lawrence
I'm sorry for breaking in, but this is a test to see if I can reach the mailing list at all. All my direct emails have been triggering error messages instead of getting through, even though as far as I know I have followed the instructions to stop them being misunderstood as list commands. PML.

Re: rndis/cdc_ether usb device causing Oops in 4.4rc1+ with NULL dereference

2015-12-31 Thread Oliver Neukum
On Thu, 2015-12-31 at 07:22 +0300, Vasily Galkin wrote: > 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 >

rndis/cdc_ether usb device causing Oops in 4.4rc1+ with NULL dereference

2015-12-30 Thread Vasily Galkin
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