From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Jeremy Lainé" <jeremy.laine@m4x.org>,
"Linux regressions mailing list" <regressions@lists.linux.dev>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org,
Paul Menzel <pmenzel@molgen.mpg.de>,
Greg KH <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83)
Date: Mon, 29 Apr 2024 20:46:00 +0200 [thread overview]
Message-ID: <8e8ca7a6-1511-4794-a214-2b75326e5484@leemhuis.info> (raw)
In-Reply-To: <CADRbXaBkkGmqnibGvcAF2YH5CjLRJ2bnnix1xKozKdw_Hv3qNg@mail.gmail.com>
On 29.04.24 20:28, Jeremy Lainé wrote:
>
> On Mon, Apr 29, 2024 at 12:24 PM Linux regression tracking (Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>>
>> So we either need to find the cause (likely a missing backport) through
>> some other way or maybe revert the culprit in the 6.1.y series. Jeremy,
>> did you try if the latter is an option? If not: could you do that
>> please? And could you also try cherry-pikcing c7eaf80bfb0c8c
>> ("Bluetooth: Fix hci_link_tx_to RCU lock usage") [v6.6-rc5] into 6.1.y
>> helps? It's just a wild guess, but it contains a Fixes: tag for the
>> commit in question.
>
> I gave it a try, and sadly I'm still hitting the exact same bug when I
> cherry-pick the patch you mentioned on top of 6.1.y (at tag v6.1.87).
>
> Thanks for trying, is there any other patch that looks like a good candidate?
Well, did you try what I suggested earlier (see above) and check if a
revert of 6083089ab00631617f9eac678df3ab050a9d837a ontop of latest 6.1.y
helps?
Ciao, Thorsten
prev parent reply other threads:[~2024-04-29 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 13:54 Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83) Jeremy Lainé
2024-04-21 21:00 ` Paul Menzel
2024-04-21 23:17 ` Jeremy Lainé
2024-04-22 5:41 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-22 8:27 ` Jeremy Lainé
2024-04-22 9:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 10:24 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 18:28 ` Jeremy Lainé
2024-04-29 18:46 ` Linux regression tracking (Thorsten Leemhuis) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e8ca7a6-1511-4794-a214-2b75326e5484@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.laine@m4x.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.