3.14.12 and option_instat_callback with 3G DONGLE

2014-07-18 Thread ressy66
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel 
log and dmesg are flooded with constant messages


option1 ttyUSB0: option_instat_callback: error -2

The device still works, it sends and receives SMS's as well,
I tried setting verbose usb debug to see if it offers any more 
explanations, but it shows nothing more.


The device is Huawei E160, but is identified as (and always has been) an 
E620


ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

Did somthing break between 3.12 and 3.14? Rather annoying at how fast 
and large kernel.log is geting.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


3.14.12 and option_instat_callback with 3G DONGLE

2014-07-18 Thread ressy66
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel 
log and dmesg are flooded with constant messages


option1 ttyUSB0: option_instat_callback: error -2

The device still works, it sends and receives SMS's as well,
I tried setting verbose usb debug to see if it offers any more 
explanations, but it shows nothing more.


The device is Huawei E160, but is identified as (and always has been) an 
E620


ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

Did somthing break between 3.12 and 3.14? Rather annoying at how fast 
and large kernel.log is geting.



--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/