syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown connection handle"

[Rolf Leggewie]

I am experiencing unstable bluetooth connections between a USB bluetooth dongle and headset. I get a ton of lines like

Dec 1 04:09:51 localhost kernel: [ 264.372205] hci_scodata_packet: hci0 SCO packet for unknown connection handle 65261

in syslog. The bluetooth connection also usually breaks down about 10 seconds into a Skype call. I cannot know if the two phenomena are actually related.

Dec 1 04:09:52 localhost kernel: [ 264.392198] hci_scodata_packet: hci0 SCO packet for unknown connection handle 65072
Dec 1 04:09:52 localhost kernel: [ 264.402199] hci_scodata_packet: hci0 SCO packet for unknown connection handle 65493
Dec 1 04:10:26 localhost bluetoothd[1756]: Audio connection got disconnected
Dec 1 04:10:26 localhost pulseaudio[1936]: ratelimit.c: 4802 events suppressed
Dec 1 04:10:35 localhost pulseaudio[1936]: ratelimit.c: 428 events suppressed

I believe this is a Ubuntu-induced regression, I was unable to reproduce the problem with a mainline kernel today.

confirmed affected: vmlinuz-2.6.32-35-generic (latest lucid kernel)
confirmed affected: vmlinuz-3.0.0-13-generic
apparently unaffected: vmlinuz-3.2.0-999-generic from today (or rather Nov 30th)

FWIW, the mainline kernel seems to have a stable bluetooth connection but syslog gets flooded there as well.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 898347

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Rolf Leggewie (r0lf)]

All the necessary information is there, I believe. I don't like to run automated scripts and upload all kinds of data to a public server. If something specific is missing, I'm happy to provide more info.

It seems somebody else had the exact same model and same problem more than two years ago already.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/39414/comments/72
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/39414/comments/73
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/39414/comments/74
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/39414/comments/75

and bug 386736

[Joseph Salisbury (jsalisbury)]

Do you happen to know if this happens with newer versions of Ubuntu as well?

[Addison Smith (lawsmith)]

This still happens with Ubuntu 12.04.

[penalvch (penalvch)]

Rolf Leggewie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Rolf Leggewie (r0lf)]

In response to #4; It happens for 3.5.0-47-generic #71~precise1-Ubuntu HWE kernel as of today.

[Rolf Leggewie (r0lf)]

The lines look like

Apr 2 00:42:57 localhost kernel: [23971.505687] Bluetooth: hci0 SCO packet for unknown connection handle 0
Apr 2 00:42:57 localhost kernel: [23971.505690] Bluetooth: hci0 SCO packet for unknown connection handle 1536
Apr 2 00:42:57 localhost kernel: [23971.505692] Bluetooth: hci0 SCO packet for unknown connection handle 48

now when running 3.13.0-20-generic in trusty. There's again thousands of them in syslog.

$ zgrep -e SCO.packet /var/log/syslog.1|wc -l
148310

[Gabriele Santilli (santilli-gabriele)]

I have a possibly related problem. The headset worked fine on 13.10 but now simply disconnects after a few seconds on 14.04.

Jul 29 13:46:22 imac kernel: [ 9194.185587] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.269541] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.594437] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac bluetoothd[791]: /org/bluez/791/hci0/dev_00_23_7F_B4_82_57/fd0: fd(24) ready
Jul 29 13:46:28 imac bluetoothd[791]: Audio connection got disconnected
Jul 29 13:46:28 imac kernel: [ 9199.993603] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:28 imac kernel: [ 9199.997737] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:41 imac kernel: [ 9213.037178] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:42 imac kernel: [ 9213.298044] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:47:21 imac kernel: [ 9252.736140] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:47:21 imac kernel: [ 9252.736147] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:47:21 imac kernel: [ 9252.736149] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:46:59 imac bluetoothd[791]: Audio connection got disconnected
Jul 29 13:49:26 imac bluetoothd[791]: Unable to get service record: Connection timed out (110)

Any ideas on what I can test?

[Gabriele Santilli (santilli-gabriele)]

ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: giesse 2725 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=971c716f-acdd-4167-a21d-55bebcae0bd5
InstallationDate: Installed on 2013-12-15 (225 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Apple Inc. iMac9,1
NonfreeKernelModules: wl nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: \boot\vmlinuz-3.13.0-32-generic ro root=UUID=07eec05d-b21a-4843-9bbf-c088d26e8642 quiet splash initrd=boot\initrd.img-3.13.0-32-generic
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
Tags: trusty
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-07-12 (16 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/27/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM91.88Z.008D.B08.0904271717
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F2218FC8
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F2218FC8
dmi.modalias: dmi:bvnAppleInc.:bvrIM91.88Z.008D.B08.0904271717:bd04/27/09:svnAppleInc.:pniMac9,1:pvr1.0:rvnAppleInc.:rnMac-F2218FC8:rvr:cvnAppleInc.:ct13:cvrMac-F2218FC8:
dmi.product.name: iMac9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Gabriele Santilli (santilli-gabriele)]

apport information

[Ville Ranki (ville-ranki)]

I believe i'm suffering from the same issue. The headset is Nokia BH-216 with Dell Latitude E6510 and Ubuntu 14.04.

Connection can work for 20 minutes, or disconnect in one. After reconnecting it again works for a while. Dmesg is flooded with lines like this:

[ 3424.806640] Bluetooth: hci0 SCO packet for unknown connection handle 6
[ 3424.806644] Bluetooth: hci0 SCO packet for unknown connection handle 6
[ 3499.700652] Bluetooth: hci0 SCO packet for unknown connection handle 6
[ 3499.700658] Bluetooth: hci0 SCO packet for unknown connection handle 6
[ 3499.700661] Bluetooth: hci0 SCO packet for unknown connection handle 6

Linux villendell 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Ville Ranki, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs