Ubuntu
linux package

Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle

Bug #1430696 reported by Ville Ranki on 2015-03-11

108

This bug affects 23 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

(I'm creating a new bug as instructed at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898347/comments/29)

I havea Nokia BH-216 bluetooth headset. Generally it works well, but randomly (after 5-15 minutes of use) it gets disconnected.

The kernel log output looks like this:

[ 3272.270382] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3272.270383] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 48
[ 3272.270385] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 3272.270386] Bluetooth: hci0 SCO packet for unknown connection handle 0

With quick googling this seems to be happening to other people with other hardware and distributions so i suppose this is a BT audio bug in kernel. Bug #898347 is related.

Tested on up to date Ubuntu 14.10 x86_64.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-31-generic 3.16.0-31.41
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: vranki 2421 F.... pulseaudio
/dev/snd/controlC1: vranki 2421 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Wed Mar 11 11:22:19 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=71d76087-3fdf-4f57-a0f4-0b128be4d386
InstallationDate: Installed on 2015-02-12 (26 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20C600LLMS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=e114ca99-f1c7-450f-a4a5-553075d92b7c ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-31-generic N/A
linux-backports-modules-3.16.0-31-generic N/A
linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET96WW (2.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C600LLMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C600LLMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600LLMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C600LLMS
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO

Tags:

Revision history for this message

Ville Ranki (ville-ranki) wrote on 2015-03-11:

AlsaInfo.txt Edit (33.8 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (63.8 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (203 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (7.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (546 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (12.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (535 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.8 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (37.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (182 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (162.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (364.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (246.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Ville Ranki (ville-ranki) wrote on 2015-03-11:

I'd like to add that i have now a different laptop (Lenovo E540) than previously, so the bug most probably isn't in the general bluetooth hardware drivers. Other people suffer from the bug with a large variety of hardware.

Revision history for this message

Brad Figg (brad-figg) wrote on 2015-03-11: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2015-03-11

Changed in linux (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2015-03-11:

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc3-vivid/

Revision history for this message

Ville Ranki (ville-ranki) wrote on 2015-03-13:

I have installed latest mainline kernel and will test next this week.

Revision history for this message

Ville Ranki (ville-ranki) wrote on 2015-03-16:

[ 2874.136892] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2874.136893] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2874.136894] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2874.136895] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 2874.136896] Bluetooth: hci0 SCO packet for unknown connection handle 0
vranki@villenthinkpad:~$ uname -a
Linux villenthinkpad 4.0.0-040000rc3-generic #201503082035 SMP Mon Mar 9 00:36:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

tags:

added: kernel-bug-exists-upstream

Revision history for this message

Torsten Harenberg (harenberg) wrote on 2015-05-30:

See the same under 15.04 running

Linux harenber-ThinkPad-X1-Carbon-3rd 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

effell (effell) wrote on 2015-06-24:

Same here, connecting a Thinkpad T420 to JBL Flip 2 speaker.
A BT dongle seems to work problem-free.

Revision history for this message

Andrea Bocci (fwyzard) wrote on 2016-10-29:

I'm having the same problem when connecting a pair of Philips SHB5950 headphones to the integrated Bluetooth controller of a Dell XPS 15 9550 (BIOS version 01.00.07).
Upstream kernels 4.6.x, 4.7.x and 4.8.x all give the same problem: the headphones pair and work fine in HSP mode, but will not switch to A2DP mode.

Revision history for this message

Levente (levente12) wrote on 2017-07-28:

#10

Same problem here.
HP ProBook 450 g4, Intel Corporation Wireless 7265, 4.10.0-28-generic, Sony SRS-XB2 . Sometimes its worked yet, but usually not. Of course with same config.

pacmd say:

>>> set-card-profile 1 a2dp_sink
Failed to set card profile to 'a2dp_sink'

Revision history for this message

David (abbasi-david) wrote on 2017-10-01:

#11

Same here.

demesg output:
[556791.335123] Bluetooth: hci0 SCO packet for unknown connection handle 0
[556791.335127] Bluetooth: hci0 SCO packet for unknown connection handle 0
[556791.345111] Bluetooth: hci0 SCO packet for unknown connection handle 0
[556791.345115] Bluetooth: hci0 SCO packet for unknown connection handle 0
[556796.711282] Bluetooth: hci0 SCO packet for unknown connection handle 260
[556796.711287] Bluetooth: hci0 SCO packet for unknown connection handle 260
uname -a
Linux lebowski 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Laptop is a Lenovo Thinkpad T550.

Revision history for this message

M Willis Monroe (willismonroe) wrote on 2018-02-06:

#12

Same here on Ubuntu 17.10 using kernel 4.15

dmesg:
[ 177.004739] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 180.384766] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 180.384861] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 180.384941] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 180.394738] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 180.394788] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 181.447392] Bluetooth: hci0: SCO packet for unknown connection handle 257
[ 181.447521] Bluetooth: hci0: SCO packet for unknown connection handle 257

and then later a repeated section of these:
[ 857.325487] Bluetooth: hci0: link tx timeout
[ 857.325530] Bluetooth: hci0: killing stalled connection 20:13:03:22:df:5e
[ 859.353861] Bluetooth: hci0: command 0x041f tx timeout
[ 861.369927] Bluetooth: hci0: command 0x0406 tx timeout

uname -a:
Linux willis-laptop 4.15.0-041500-generic #201801282230 SMP Sun Jan 28 22:31:30 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Pedro Arthur Duarte (JEdi) (pedroarthur-jedi) wrote on 2018-03-05:

#13

This occurred to me. The log files got around 15GB. I had to enable $RepeatedMsgReduction in rsyslogd in order to avoid filling my disk.

Revision history for this message

Claudio Kuenzler (napsty) wrote on 2018-09-17:

#14

Same problem here on a DELL Latitude E7440 with Linux Mint 17.3 (based on Ubuntu 14.04 LTS) installed.
When I use a Plantronics Voyager which connects directly to the notebook's internal bluetooth chip, I get these dmesg entries:

$ dmesg | grep -i Bluetooth
[ 3.994061] Bluetooth: Core ver 2.21
[ 3.994078] Bluetooth: HCI device and connection manager initialized
[ 3.994082] Bluetooth: HCI socket layer initialized
[ 3.994085] Bluetooth: L2CAP socket layer initialized
[ 3.994095] Bluetooth: SCO socket layer initialized
[ 4.014377] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.014381] Bluetooth: BNEP filters: protocol multicast
[ 4.014384] Bluetooth: BNEP socket layer initialized
[ 4.017044] Bluetooth: RFCOMM TTY layer initialized
[ 4.017049] Bluetooth: RFCOMM socket layer initialized
[ 4.017054] Bluetooth: RFCOMM ver 1.11
[ 4.119489] Bluetooth: hci0: read Intel version: 370710018002030d37
[ 4.119491] Bluetooth: hci0: Intel device is already patched. patch num: 37
[ 32.154782] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 32.164817] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 32.164821] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.934811] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.934815] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 572.934817] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 641.073418] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 646.105832] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 646.105837] Bluetooth: hci0 SCO packet for unknown connection handle 257
[ 646.105839] Bluetooth: hci0 SCO packet for unknown connection handle 257

The headset is not correctly recognized. Sometimes works, sometimes doesn't (sound output works better than input, microphone seems not available). In VMware Player, the headset is not recognized to add as a removable device into the VM.

However if I use an almost identical headset, also a Plantronics Voyager but with a bluetooth usb dongle, I get no problems at all and I am able to add it as a removable device into the VM.

So same OS, same hardware but different handling of internal bluetooth vs. bluetooth dongle.

Same problem here on a DELL Latitude E7440 with Linux Mint 17.3 (based on Ubuntu 14.04 LTS) installed. 
When I use a Plantronics Voyager which connects directly to the notebook's internal bluetooth chip, I get these dmesg entries:

$ dmesg | grep -i Bluetooth
[    3.994061] Bluetooth: Core ver 2.21
[    3.994078] Bluetooth: HCI device and connection manager initialized
[    3.994082] Bluetooth: HCI socket layer initialized
[    3.994085] Bluetooth: L2CAP socket layer initialized
[    3.994095] Bluetooth: SCO socket layer initialized
[    4.014377] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.014381] Bluetooth: BNEP filters: protocol multicast
[    4.014384] Bluetooth: BNEP socket layer initialized
[    4.017044] Bluetooth: RFCOMM TTY layer initialized
[    4.017049] Bluetooth: RFCOMM socket layer initialized
[    4.017054] Bluetooth: RFCOMM ver 1.11
[    4.119489] Bluetooth: hci0: read Intel version: 370710018002030d37
[    4.119491] Bluetooth: hci0: Intel device is already patched. patch num: 37
[   32.154782] Bluetooth: hci0 SCO packet for unknown connection handle 0
[   32.164817] Bluetooth: hci0 SCO packet for unknown connection handle 0
[   32.164821] Bluetooth: hci0 SCO packet for unknown connection handle 0
[  572.934811] Bluetooth: hci0 SCO packet for unknown connection handle 0
[  572.934815] Bluetooth: hci0 SCO packet for unknown connection handle 0
[  572.934817] Bluetooth: hci0 SCO packet for unknown connection handle 0
[  641.073418] Bluetooth: hci0 SCO packet for unknown connection handle 0
[  646.105832] Bluetooth: hci0 SCO packet for unknown connection handle 257
[  646.105837] Bluetooth: hci0 SCO packet for unknown connection handle 257
[  646.105839] Bluetooth: hci0 SCO packet for unknown connection handle 257

However if I use an almost identical headset, also a Plantronics Voyager but with a bluetooth usb dongle, I get no problems at all and I am able to add it as a removable device into the VM.

So same OS, same hardware but different handling of internal bluetooth vs. bluetooth dongle.

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Revision history for this message

Richard Cooper (i-ololosha228-i) wrote on 2020-03-30:

#15

wait a minute... is this bug existend about 5 years, and nobody fixed it? same crap here,

i built 5.3 kernel month ago, but problem is not with kernel, maybe with usb driver module, or something.

dmesg -l err:
[ 11.456051] ccp 0000:27:00.2: sev command 0x4 timed out, disabling PSP
[ 11.456055] ccp 0000:27:00.2: SEV: failed to get status. Error: 0x0
[ 8723.273929] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 8723.273935] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 8723.273937] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 8723.283957] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 9713.725625] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[ 9713.725636] debugfs: File 'le_max_key_size' in directory 'hci0' already present!

hciconfig hci0 -a:
hci0: Type: Primary Bus: USB
BD Address: 18:56:80:48:F8:D1 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:358964 acl:4599 sco:4936 events:2405 errors:0
TX bytes:893887 acl:1189 sco:4923 commands:761 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'computer'
Class: 0x1c0104
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 4.2 (0x8) Revision: 0x1100
LMP Version: 4.2 (0x8) Subversion: 0x1100
Manufacturer: Intel Corp. (2)

uname -a:
Linux computer 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

rumpl (rumplstielz) wrote on 2020-05-12:

#16

Same for Sennheiser MOMENTUM M2 AEBT in Ubuntu 20.04

ii bluez 5.53-0ubuntu3 amd64 Bluetooth tools and daemons
ii bluez-cups 5.53-0ubuntu3 amd64 Bluetooth printer driver for CUPS
ii bluez-obexd 5.53-0ubuntu3 amd64 bluez obex daemon
ii libbluetooth3:amd64 5.53-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack

Revision history for this message

Vlad (sangemaru) wrote on 2020-07-01:

#17

Same for pretty much all my bluetooth headsets (Skullcandy Uproar Wireless, Plantronics E50 or M70 & others).

On Ubuntu 20.10, kernel Linux 5.7.0-050700-generic

01.07.2020 12:02 pulseaudio SCO packet received of unaligned size: 5
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 4093
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 3
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 1535
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 4093
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 4095
01.07.2020 12:02 kernel Bluetooth: hci0: SCO packet for unknown connection handle 4095

Revision history for this message

Vlad (sangemaru) wrote on 2020-07-01:

#18

╰─ hciconfig hci0 -a
hci0: Type: Primary Bus: USB
BD Address: 9C:B6:D0:E2:25:58 ACL MTU: 1024:8 SCO MTU: 50:8
UP RUNNING PSCAN
RX bytes:54258861 acl:42 sco:1063465 events:11592 errors:0
TX bytes:54182045 acl:78 sco:1061223 commands:11381 errors:143
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'blackthorne-XPS-15-9560'
Class: 0x1c010c
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8) Revision: 0x0
LMP Version: 4.2 (0x8) Subversion: 0x25a
Manufacturer: Qualcomm (29

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package