Re: USB regression in next-20171108 with hub spamming

* Felipe Balbi [171109 11:01]: > Felipe Balbi writes: > > Okay, found it. Testing a patch. > > Here's the patch, I'll send it formally shortly. Thanks yeah that fixes the issue for me, replied to your formal patch with a tested by.

Re: USB regression in next-20171108 with hub spamming

Hi, Felipe Balbi writes: > Felipe Balbi writes: > >> Felipe Balbi writes: >> >>> Hi, >>> >>> Greg Kroah-Hartman writes: On Wed, Nov 08, 2017 at 03:05:11PM -0800, Tony

Re: USB regression in next-20171108 with hub spamming

Felipe Balbi writes: > Felipe Balbi writes: > >> Hi, >> >> Greg Kroah-Hartman writes: >>> On Wed, Nov 08, 2017 at 03:05:11PM -0800, Tony Lindgren wrote: Hi Felipe & Greg, Looks like in

Re: USB regression in next-20171108 with hub spamming

Felipe Balbi writes: > Hi, > > Greg Kroah-Hartman writes: >> On Wed, Nov 08, 2017 at 03:05:11PM -0800, Tony Lindgren wrote: >>> Hi Felipe & Greg, >>> >>> Looks like in next-20171108 USB hub is spamming console about once a >>> second

Re: USB regression in next-20171108 with hub spamming

Hi, Greg Kroah-Hartman writes: > On Wed, Nov 08, 2017 at 03:05:11PM -0800, Tony Lindgren wrote: >> Hi Felipe & Greg, >> >> Looks like in next-20171108 USB hub is spamming console about once a >> second after commit 7dfd74fd128 ("Merge remote-tracking branch >>

Re: USB regression in next-20171108 with hub spamming

On Wed, Nov 08, 2017 at 03:05:11PM -0800, Tony Lindgren wrote: > Hi Felipe & Greg, > > Looks like in next-20171108 USB hub is spamming console about once a > second after commit 7dfd74fd128 ("Merge remote-tracking branch > 'usb/usb-next'"). > > Any ideas? See the log below. Any chance you can