New: AX200 Bluetooth audio devices disconnect after random intervals
https://bugzilla.kernel.org/show_bug.cgi?id=211969
Bug ID: 211969
Summary: AX200 Bluetooth audio devices disconnect after random
intervals
Product: Drivers
Version: 2.5
Kernel Version: 5.11.1
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: NoI've personally observed this issue on kernels 5.10 and 5.11. Connecting my headphones with both PulseAudio and PipeWire causes disconnects since a linux-firmware package upgrade (20210208.b79d239-1, Arch Linux). Downgrading the package to 20201218.646f159-1 solves my problem. The bug causes my headphones to disconnect after anywhere from 5 minutes to 3 hours, though I found PipeWire causes the disconnect to happen closer to the 30 minute range.
There are a few user accounts posting about their experiences with this in the following links:
https://bbs.archlinux.org/viewtopic.php?pid=1957011#p1957011
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/732
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 211969] AX200 Bluetooth audio devices disconnect after random intervals
https://bugzilla.kernel.org/show_bug.cgi?id=211969
Jackson McClintock ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Jackson McClintock ([email protected]) --- I looked at the commits from version 20201218 to 20210208 of linux-firmware and found 3 commits which updated the firmware for Intel Bluetooth AX200, AX201, and AX210, which are the cards others and I seem to be having issues with. I'm pretty sure this firmware is proprietary, so I don't know the best way to try to get a fix for this bug, since kernel developers don't have access to the source code. I did notice that that these were updated again, though, but the bug stills exists as of linux-firmware version 20210315.
These are the links to the original commits that probably created this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=3027ae40cf3e43725c45e53085b5e0484f09ea71
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=13979c3a51d068fc1b66df1065d9479bddcb418f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d33d2d86ce3ad2ed1a4e196840fdd3a814d34433
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.