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 09:14:02 +0000 [thread overview]
Message-ID: <bug-220419-62941-PR5yA3V9eg@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 #3 from Anton Ekblad (anton@ekblad.cc) ---
(In reply to Luiz Von Dentz from comment #1)
> As far I know BE201 still use btusb, not really sure why a change to
> btintel_pcie would have any effect on a device over btusb but perhaps there
> is something changed that affect btintel which is shared between both.
I don't think that is correct. lspci describes the card as "00:14.7 Bluetooth
[0d11]: Intel Corporation Device [8086:a876] (rev 10)", Intel says it's an
CNVio card [1] (which I think is pcie only?), the problematic commit only
touches btintel_pcie.{c,h}, and btusb is not even loaded on my system (neither
before nor after the regression).
[1]
https://www.intel.com/content/www/us/en/products/sku/230079/intel-wifi-7-be201/specifications.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2025-08-06 9:14 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
2025-08-06 9:14 ` bugzilla-daemon [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=bug-220419-62941-PR5yA3V9eg@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