Re: cdc_ether flooding kernel logs since bfe9b9d2d

Hi, On Wed, Nov 30, 2016 at 4:17 PM, Oliver Neukum wrote: > On Tue, 2016-11-29 at 14:41 +0100, Kristian Evensen wrote: >> I don't know which of the two behaviors (if any) are "correct" or what >> the best way to solve this problem is. One options is to remove the >> code from

Re: cdc_ether flooding kernel logs since bfe9b9d2d

On Tue, 2016-11-29 at 14:41 +0100, Kristian Evensen wrote: > I don't know which of the two behaviors (if any) are "correct" or what > the best way to solve this problem is. One options is to remove the > code from the generic usbnet_cdc_status() function and move it to a > ZTE-specific status

Re: cdc_ether flooding kernel logs since bfe9b9d2d

Hi, On Tue, Nov 29, 2016 at 11:27 AM, Henning Schild wrote: > commit bfe9b9d2d introduced a workaround for link status detection. > That workaround seems to cause a tight loop of usbnet_cdc_status being > called all the time, which in turn prints > "kevent 11 may have

cdc_ether flooding kernel logs since bfe9b9d2d

Hi, commit bfe9b9d2d introduced a workaround for link status detection. That workaround seems to cause a tight loop of usbnet_cdc_status being called all the time, which in turn prints "kevent 11 may have been dropped" in the kernel log all the time. I am not sure about the semantics, i just