Hide Forgot
Created attachment 546387 [details] The sort of stuff in the kernel message buffer Description of problem: After pairing my Bluetooth headset, I see a large amount of Bluetooth: hci0 SCO packet for unknown connection handle (16-bit uint) and similar in the kernel message buffer (see attached for an example). Bluetooth dongle is a USB 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) device. Version-Release number of selected component (if applicable): kernel-3.1.5-1.fc16.x86_64 bluez-4.96-3.fc16.x86_64 How reproducible: Always. Steps to Reproduce: 1. Pair my BH95 Bluetooth headset. Actual results: Logspam. Sometimes the headset pairs but no audio can be played. Expected results: No spam. Consistent audio service.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
(In reply to comment #3) > [mass update] > kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. > Please retest with this update. Still present with 3.3.0-4.fc16.x86_64. Same results as before, headset doesn't work immediately after pairing.
I can see the same problem with my Jabra Sport bluetooth headset. The same kernel messages and the headset shows Connected status and immediately Disconnect. I'm using F17 kernel-3.4.4-5.fc17.x86_64.
The same problem with the Sony MW600 headset. It got paired without problem but Gnome3 refuses to connect to it. F17 kernel 3.4.3-1.fc17.x86_64 Bluetooth adapter Broadcom BCM2046 Bluetooth headset Sony MW600 dmesg output: [ 1120.067466] input: 8C:64:22:BE:42:6F as /devices/virtual/input/input14 [ 1120.178223] Bluetooth: hci0 SCO packet for unknown connection handle 1 [ 1120.178228] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.178231] Bluetooth: hci0 SCO packet for unknown connection handle 256 [ 1120.188216] Bluetooth: hci0 SCO packet for unknown connection handle 65535 [ 1120.188222] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188226] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188229] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188232] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188236] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188239] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188242] Bluetooth: hci0 SCO packet for unknown connection handle 0 [ 1120.188245] Bluetooth: hci0 SCO packet for unknown connection handle 0
Still seeing this with F17 kernel 3.6.2-2.fc17.x86_64.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.
I'm still seeing this on kernel-3.7.4-204.fc18.x86_64. kernel-3.8.0-0.rc4.git3.1.fc19.x86_64 crashes (dmesg attached). kernel-3.8.0-0.rc4.git5.1.fc19.x86_64 reports an inconsistent lock state (dmesg attached).
Created attachment 687595 [details] dmesg for 3.8.0-0.rc4.git3.1.fc19.x86_64
Created attachment 687596 [details] dmesg for 3.8.0-0.rc4.git5.1.fc19.x86_64
*** Bug 976320 has been marked as a duplicate of this bug. ***
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
I still notice the SCO deluge and holes in audio stream with a VH410 headset, but only if I connect the headset while an audio stream is in progress (e.g., a Skype conversation). If the headset is connected *before* the conversation starts, it appears to work normally. Kernel version: 3.11.4-201.fc19.x86_64 Headset: VH410 PC: ASUS UX31E
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
(In reply to Justin M. Forbes from comment #16) With kernel version 3.12.6-200.fc19, the SCO messages appear only at the begin of a BT connection, e.g., while the SKype Test Call is ongoing. But now the SCO messages stop after a few seconds, while before they were going on for the whole duration of the audio. I still have managed to have SCO messages continuously flooding while overlapping a Linphone (VoIP) call over the end of a Skype call, but I cannot reproduce it reliably. Basically, I think that it works reliable enough now and the report can be closed.
Thanks for the update.