From: Mike <user.service2016@gmail.com>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
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>,
"Jeremy Lainé" <jeremy.laine@m4x.org>,
"Linux regressions mailing list" <regressions@lists.linux.dev>
Subject: Re: Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83)
Date: Tue, 28 May 2024 22:54:27 +0200 [thread overview]
Message-ID: <c947e600-e126-43ea-9530-0389206bef5e@gmail.com> (raw)
In-Reply-To: <8e8ca7a6-1511-4794-a214-2b75326e5484@leemhuis.info>
On 29.04.24 20:46, Linux regression tracking (Thorsten Leemhuis) wrote:>
Well, did you try what I suggested earlier (see above) and check if a
> revert of 6083089ab00631617f9eac678df3ab050a9d837a ontop of latest 6.1.y
> helps?
Hello Thorsten, Jeremy,
I hope you don't mind if I jump into the conversation trying to help.
I'm also experiencing this bug (with an Intel AX200) and I don't see
any updates in this thread since a month.
I tried reverting 6083089ab00631617f9eac678df3ab050a9d837a
on top of6.1.91 and it looks much better: it's been 10 days, and the BT
and the system are stable.
Previously, I encountered the mentioned "kernel BUG" at each boot, and I
was unable to stop/kill the bluetoothd process.
Let me know if/how I can help further.
M.
next prev parent reply other threads:[~2024-05-28 20:54 UTC|newest]
Thread overview: 28+ 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)
2024-05-28 20:54 ` Mike [this message]
2024-05-29 9:06 ` Thorsten Leemhuis
2024-06-03 20:03 ` Mike
2024-06-06 10:18 ` Thorsten Leemhuis
2024-06-12 12:04 ` Greg KH
2024-06-18 10:30 ` Thorsten Leemhuis
2024-10-31 6:33 ` Salvatore Bonaccorso
2024-11-05 17:29 ` Thorsten Leemhuis
2024-11-05 17:53 ` Luiz Augusto von Dentz
2024-11-05 19:23 ` Salvatore Bonaccorso
2024-11-06 7:23 ` Salvatore Bonaccorso
2024-11-06 7:26 ` Greg KH
2024-11-06 7:40 ` Salvatore Bonaccorso
2024-11-06 15:02 ` Luiz Augusto von Dentz
2024-11-07 4:38 ` Greg KH
2024-11-12 11:54 ` Thorsten Leemhuis
2024-11-12 12:04 ` Greg KH
2024-11-13 15:10 ` Greg KH
2024-11-15 17:56 ` Salvatore Bonaccorso
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=c947e600-e126-43ea-9530-0389206bef5e@gmail.com \
--to=user.service2016@gmail.com \
--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@leemhuis.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).