Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 13BF1C433EF for ; Sat, 4 Dec 2021 11:06:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350214AbhLDLKB (ORCPT ); Sat, 4 Dec 2021 06:10:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230102AbhLDLKA (ORCPT ); Sat, 4 Dec 2021 06:10:00 -0500 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBA9EC061751; Sat, 4 Dec 2021 03:06:34 -0800 (PST) Received: from ip4d173d4a.dynamic.kabel-deutschland.de ([77.23.61.74] helo=[192.168.66.200]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1mtSsD-0003mW-AQ; Sat, 04 Dec 2021 12:06:33 +0100 Message-ID: <7d5df080-0564-f265-f0b3-eb3dbca41599@leemhuis.info> Date: Sat, 4 Dec 2021 12:06:32 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Subject: Re: Regression: plugging in USB scanner breaks all USB functionality Content-Language: en-BS To: Greg KH Cc: regressions@lists.linux.dev, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org References: <35f7428b39f996c793f5b4a6a314772681c73d7a.camel@apache.org> <3eb9c3f8-6bca-da08-47ec-af2a02d6a485@leemhuis.info> <73b325e3-d5d9-f768-9033-3aa0d3683e47@leemhuis.info> From: Thorsten Leemhuis In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1638615994;65b5bb11; X-HE-SMSGID: 1mtSsD-0003mW-AQ Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04.12.21 11:44, Greg KH wrote: > On Sat, Dec 04, 2021 at 11:26:45AM +0100, Thorsten Leemhuis wrote: >> >> On 04.12.21 11:03, Greg KH wrote: >>> 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, >> >> Yeah, sorry, after sending that mail it occurred to me that this wasn't >> ideal and hard to follow. >> >> I got it from here: >> https://lore.kernel.org/lkml/a649395b-0b91-a0d2-c510-ea8ec4aef917@linux.intel.com/ >> >> I already decided that next time something like this comes up I'll reply >> to the mail with the details instead (with proper quoting) to make this >> easier to follow. >> >> Reading that message again I suspect that I might have been a bit quick >> as well, as this might not be the commit id this ends up with when it >> gets merged: I now see that this is likely a developers tree and not one >> that gets indirectly merged. >> >> Sorry, I'll manually keep an eye on things to fix this up once that >> patch gets its real it. > > Ah, found it, it's now in my usb-linus branch, and I'll send it to Linus > later today: > 09f736aa9547 ("xhci: Fix commad ring abort, write all 64 bits to CRCR register.") Great, thx for letting me known, then I will let regzbot know: #regbzot fixed-by: 09f736aa9547 TWIMC: regbzot will automatically pick up the title once it sees the commit in next or mainline. Ciao, Thorsten