From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [85.220.165.71]) (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 A8AFD7C for ; Tue, 4 Apr 2023 12:17:44 +0000 (UTC) Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[127.0.0.1]) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1pjfba-0004fD-3q; Tue, 04 Apr 2023 14:17:42 +0200 Message-ID: <11b65b4e-1b2e-d5d8-9ab8-f7d7f5238157@pengutronix.de> Date: Tue, 4 Apr 2023 14:17:39 +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.0 Subject: Re: [BUG] BLE device unpairing triggers kernel panic Content-Language: en-US To: Linux regressions mailing list , Luiz Augusto von Dentz Cc: "linux-bluetooth@vger.kernel.org" , Marcel Holtmann , 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> From: Ahmad Fatoum In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2a0a:edc0:0:900:1d::77 X-SA-Exim-Mail-From: a.fatoum@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: regressions@lists.linux.dev Hello Thorsten, On 04.04.23 14:14, Linux regression tracking #update (Thorsten Leemhuis) wrote: > [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: No. It's still broken for me, but now the kernel warning that came along with it is gone. I am discussing this with Luiz still on Github, but this regression is _not_ resolved. Thanks, Ahmad > > #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. > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |