From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220419] Bluetooth stops working on Intel BE201 a few seconds after connecting a BT peripheral
Date: Wed, 06 Aug 2025 06:39:11 +0000 [thread overview]
Message-ID: <bug-220419-62941-HZ0WhyKH38@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220419-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220419
--- Comment #2 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Details for the bisected commit [1]:
$ git describe 6ed83047389c63a8d7712b0bf19eb38a6e4dc68e
v6.14-rc7-1458-g6ed83047389c
$ git show 6ed83047389c63a8d7712b0bf19eb38a6e4dc68e
commit 6ed83047389c63a8d7712b0bf19eb38a6e4dc68e
Author: Kiran K <kiran.k@intel.com>
Date: Tue Feb 25 17:13:10 2025 +0530
Bluetooth: btintel_pcie: Setup buffers for firmware traces
This patch allocates the host memory which is used by controller to dump
the firmware traces. The memory needs to be shared with controller via
context information.
Co-developed-by: Vijay Satija <vijay.satija@intel.com>
Signed-off-by: Vijay Satija <vijay.satija@intel.com>
Signed-off-by: Kiran K <kiran.k@intel.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
[…]
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6ed83047389c63a8d7712b0bf19eb38a6e4dc68e
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-08-06 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 21:43 [Bug 220419] New: Bluetooth stops working on Intel BE201 a few seconds after connecting a BT peripheral bugzilla-daemon
2025-08-05 22:34 ` [Bug 220419] " bugzilla-daemon
2025-08-06 6:39 ` bugzilla-daemon [this message]
2025-08-06 9:14 ` bugzilla-daemon
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=bug-220419-62941-HZ0WhyKH38@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@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