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 15DDA7C for ; Tue, 4 Apr 2023 12:14:53 +0000 (UTC) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1pjfYo-0007I6-JD; Tue, 04 Apr 2023 14:14:50 +0200 Message-ID: Date: Tue, 4 Apr 2023 14:14:50 +0200 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:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [BUG] BLE device unpairing triggers kernel panic Content-Language: en-US, de-DE From: "Linux regression tracking #update (Thorsten Leemhuis)" To: Ahmad Fatoum , Luiz Augusto von Dentz Cc: "linux-bluetooth@vger.kernel.org" , Marcel Holtmann , "regressions@lists.linux.dev" , Pengutronix Kernel Team , Tedd Ho-Jeong An References: <8d5c4724-d511-39b1-21d7-116c91cada45@pengutronix.de> <1d1b76cf-df6f-3935-5cd2-c45ea78f2c33@pengutronix.de> <1a5ec80d-690f-285c-3da8-ccdaf5516d85@pengutronix.de> <577c7140-a30c-ca06-a81e-c791e44b1321@pengutronix.de> <12cafbc4-39a2-1bea-c1d1-2cad406c8b83@leemhuis.info> Reply-To: Linux regressions mailing list In-Reply-To: <12cafbc4-39a2-1bea-c1d1-2cad406c8b83@leemhuis.info> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1680610494;baafb3d5; X-HE-SMSGID: 1pjfYo-0007I6-JD [TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 17.08.22 12:24, Thorsten Leemhuis wrote: > On 07.07.22 07:45, Ahmad Fatoum wrote: >> On 04.07.22 14:11, Thorsten Leemhuis wrote: >>> Hi, this is your Linux kernel regression tracker. Top-posting for once, >>> to make this easily accessible to everyone. >>> >>> Looks like the discussions to fix this regression got stuck. What can be >>> done to get thing rolling again? Or has progress been made and I just >>> missed it? Ciao, Thorsten >> >> No progress has been made as far as I am aware. I am reverting the commit >> introducing the regression on my systems and haven't yet had the time to >> debug this further to help find an alternative solution. > > Just wondering: still no progress I assume? > > Anyway: I'm putting it on the backburner to get it out of the > spot-light, as this doesn't look urgent and things seems to progress > very slowly. > > #regzbot backburner: debuging is slow this further Great, I see (from interpreting https://lore.kernel.org/all/04377d2a-4d97-0345-18a1-1f18533436fe@pengutronix.de/ [thx!] and looking at the described errors) that this was finally addressed: #regzbot fix: 2731e038a76d #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.