From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 38896173 for ; Tue, 28 Dec 2021 13:37:23 +0000 (UTC) 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 1n2CfJ-00064L-Cf; Tue, 28 Dec 2021 14:37:21 +0100 Message-ID: <093aeb47-89ef-2fc0-be88-4082847eca0a@leemhuis.info> Date: Tue, 28 Dec 2021 14:37:21 +0100 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH] fix 5.15 init regression for Intel Bluetooth #forregzbot Content-Language: en-BS From: Thorsten Leemhuis To: "regressions@lists.linux.dev" References: <856c5dc7-9fb4-8438-3451-7b369832056a@odi.ch> <246bd180-4d8f-ae2b-1b51-90eaf194803c@leemhuis.info> <3b17319c-2ad7-bc5a-4350-076afe4d5e65@leemhuis.info> In-Reply-To: <3b17319c-2ad7-bc5a-4350-076afe4d5e65@leemhuis.info> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1640698643;56c3ff0b; X-HE-SMSGID: 1n2CfJ-00064L-Cf On 28.12.21 13:52, Thorsten Leemhuis wrote: > #regzbot dup-of: > https://lore.kernel.org/linux-bluetooth/s5h5ys4sjke.wl-tiwai@suse.de/ Sorry for the noise, this is the mail with the report: #regzbot dup-of: https://lore.kernel.org/linux-bluetooth/20211202162256.31837-1-tiwai@suse.de/ > TWIMC: this mail is primarily send for documentation purposes and for > regzbot, my Linux kernel regression tracking bot. These mails usually > contain '#forregzbot' in the subject, to make them easy to spot and filter. > > On 28.12.21 08:20, Thorsten Leemhuis wrote: >> [TLDR: I'm adding this regression to regzbot, the Linux kernel >> regression tracking bot; most text you find below is compiled from a few >> templates paragraphs some of you might have seen already.] >> >> On 27.12.21 11:26, Ortwin Glück wrote: >>> >>> On all 5.15 kernels the Intel Bluetooth no longer works. All was fine in >>> 5.14. >>> Apparently the quirk is needed for this device. >>> >>> vanilla 5.15.5: >>>    Bluetooth: hci0: Reading Intel version command failed (-110) >>>    Bluetooth: hci0: command tx timeout >>> >>> with patch: >>>    Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014 >>>    Bluetooth: hci0: Intel device is already patched. patch num: 32 >>> >>> Please apply to stable too. >> >> Hi, this is your Linux kernel regression tracker speaking. >> >> Thanks for the report. >> >> Adding the regression mailing list to the list of recipients, as it >> should be in the loop for all regressions, as explained here: >> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html >> >> 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..v5.15 >> #regzbot title bluetooth: Intel Bluetooth no longer works >> #regzbot ignore-activity >> >> Reminder: when fixing the issue, please add a 'Link:' tag with the URL >> to the report (the parent of this mail) using the kernel.org redirector, >> as explained in 'Documentation/process/submitting-patches.rst'. Regzbot >> then will automatically mark the regression as resolved once the fix >> lands in the appropriate tree. For more details about regzbot see footer. >> >> Sending this to everyone that got the initial report, to make all aware >> of the tracking. I also hope that messages like this motivate people to >> directly get at least the regression mailing list and ideally even >> regzbot involved when dealing with regressions, as messages like this >> wouldn't be needed then. >> >> Don't worry, I'll send further messages wrt to this regression just to >> the lists (with a tag in the subject so people can filter them away), as >> long as they are intended just for regzbot. With a bit of luck no such >> messages will be needed anyway. >> >> Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat). >> >> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports >> on my table. I can only look briefly into most of them. Unfortunately >> therefore I sometimes will get things wrong or miss something important. >> I hope that's not the case here; if you think it is, don't hesitate to >> tell me about it in a public reply. That's in everyone's interest, as >> what I wrote above might be misleading to everyone reading this; any >> suggestion I gave thus might sent someone reading this down the wrong >> rabbit hole, which none of us wants. >> >> BTW, I have no personal interest in this issue, which is tracked using >> regzbot, my Linux kernel regression tracking bot >> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting >> this mail to get things rolling again and hence don't need to be CC on >> all further activities wrt to this regression. >> >> --- >> Additional information about regzbot: >> >> If you want to know more about regzbot, check out its web-interface, the >> getting start guide, and/or the references documentation: >> >> https://linux-regtracking.leemhuis.info/regzbot/ >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md >> >> The last two documents will explain how you can interact with regzbot >> yourself if your want to. >> >> Hint for reporters: when reporting a regression it's in your interest to >> tell #regzbot about it in the report, as that will ensure the regression >> gets on the radar of regzbot and the regression tracker. That's in your >> interest, as they will make sure the report won't fall through the >> cracks unnoticed. >> >> Hint for developers: you normally don't need to care about regzbot once >> it's involved. Fix the issue as you normally would, just remember to >> include a 'Link:' tag to the report in the commit message, as explained >> in Documentation/process/submitting-patches.rst >> That aspect was recently was made more explicit in commit 1f57bd42b77c: >> https://git.kernel.org/linus/1f57bd42b77c >>