On Fri, Dec 03, 2021 at 06:24:52PM +0100, Thorsten Leemhuis wrote: > On 02.12.21 16:13, Thorsten Leemhuis wrote: > > Hi, this is your Linux kernel regression tracker speaking. > > > > Thanks for the report. > > > > Top-posting for once, to make this easy accessible to everyone. > > > > FWIW, 5.14 is EOL, so it might not be fixed there. As the problem is in > > newer kernels as well, I suspect that it was a change applies to 5.15 or > > 5.16 that got backported. Maybe one of the developers might have an idea > > which commit causes it. If that's not the case you likely should try a > > bisection to find the culprit. Performing one between v5.14.11..v5.14.14 > > is likely the easiest and quickest way to find it. > > > > To be sure this issue doesn't fall through the cracks unnoticed, I'm > > adding it to regzbot, my Linux kernel regression tracking bot: > > > > #regzbot ^introduced v5.14.11..v5.14.14 > > #regzbot title usb: plugging in USB scanner breaks all USB functionality > > [regression present in 5.15.2 und 5.16-rc3, too] > > #regzbot ignore-activity > > #regzbot introduced ff0e50d3564f > #regzbot fixed-by 385b5b09c3546c87cfb730b76abe5f8d73c579a2 Odd, where did that git commit id come from? I don't see it in linux-next or Linus's tree. confused, greg k-h
