**Fix patch resolves a similar issue on different hardware**
I experienced a similar regression on 7.0.0-10-generic with a different
Bluetooth device. I applied the fix patch from Luiz Augusto von Dentz
for kernel commit 6c3ea155e5ee ("Bluetooth: L2CAP: Fix not tracking
outstanding TX ident") and it resolved my issue.
The commit, which landed in v7.0-rc1, changes L2CAP transaction
identifier allocation to use ida_alloc_range, which reuses idents more
aggressively than the previous approach. Since L2CAP underlies all
Bluetooth profiles, this can potentially affect any profile.
Patch:
https://lore.kernel.org/linux-bluetooth/[email protected]/
Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=221177,
https://bugzilla.kernel.org/show_bug.cgi?id=221120
My test details:
- Kernel: 7.0.0-10-generic (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
- Source built from: apt source linux (7.0.0-10.10)
- Adapter: Intel Bluetooth (btintel/btusb)
- Device: FiiO BTR5 (A2DP sink, only BT device tested)
- Symptom: A2DP audio transport dropped within ~5-20 seconds, BT link stayed
connected. Same "a2dp-sink profile connect failed: Device or resource busy"
error as the original report.
- After patching net/bluetooth/bluetooth.ko: A2DP audio stable
** Bug watch added: Linux Kernel Bug Tracker #221177
https://bugzilla.kernel.org/show_bug.cgi?id=221177
** Bug watch added: Linux Kernel Bug Tracker #221120
https://bugzilla.kernel.org/show_bug.cgi?id=221120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
