On kernel 6.9.7, I get several errors "Bluetooth: hci0: corrupted SCO packet" on dmesg while playing audio. On the user side, the Edifier W800BT audio is interrupted by several seconds and gets back by itself. It happens at least once every minute. Reverting to 6.6.36 LTS solves the issue. The dongle used is Baseus BA04 Bluetooth 5.1 Usb. Below is the messages on linux 6.6.36: braulio @ phoenix ➜ ~ sudo dmesg | grep -i bluetooth [ 131.956823] Bluetooth: Core ver 2.22 [ 131.956851] NET: Registered PF_BLUETOOTH protocol family [ 131.956852] Bluetooth: HCI device and connection manager initialized [ 131.956855] Bluetooth: HCI socket layer initialized [ 131.956857] Bluetooth: L2CAP socket layer initialized [ 131.956860] Bluetooth: SCO socket layer initialized [ 131.981550] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=0001 [ 131.981554] Bluetooth: hci0: LMP ver=9 subver=0001; manufacturer=2279 [ 131.981555] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [ 131.981556] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [ 131.981558] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [ 131.981558] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [ 131.981559] Bluetooth: hci0: HCI Set Event Filter command not supported. [ 132.050598] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 132.050603] Bluetooth: BNEP filters: protocol multicast [ 132.050607] Bluetooth: BNEP socket layer initialized [ 132.631669] Bluetooth: MGMT ver 1.22 [ 132.677355] Bluetooth: RFCOMM TTY layer initialized [ 132.677364] Bluetooth: RFCOMM socket layer initialized [ 132.677367] Bluetooth: RFCOMM ver 1.11
A few notes from a bystander: * please attached a dmesg from a kernel where this problem occurs, ideally with the latest 6.10-rc version or newer * no developer might look into this, unless you bisect which change causes the problem, as then someone is obliged to fix it (https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html ) * not sure, the bluetooth developers might not even see this report (search for bugzilla on https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/ for details)
I can't reproduce it anymore, so I'll close it for now