Failed to add UUID: Busy (0x0a)

Bug #1867147 reported by raimundoguimaraes1
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

dmesg

Bluetooth: hci0: command 0x0c24 tx timeout

rfkill list

0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: hci1: Bluetooth
 Soft blocked: no
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: yes
 Hard blocked: no

bluetoothctl

Failed to start discovery: org.bluez.Error.InProgress

lsusb

Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

lshw

*-usb
             descrição: USB controller
             produto: Cannon Lake PCH USB 3.1 xHCI Host Controller
             fabricante: Intel Corporation
             ID físico: 14
             informações do barramento: pci@0000:00:14.0
             versão: 10
             largura: 64 bits
             clock: 33MHz
             capacidades: pm msi xhci bus_master cap_list
             configuração: driver=xhci_hcd latency=0
             recursos: irq:124 memória:eb220000-eb22ffff
           *-usbhost:0
                produto: xHCI Host Controller
                fabricante: Linux 5.3.0-40-generic xhci-hcd
                ID físico: 0
                informações do barramento: usb@1
                nome lógico: usb1
                versão: 5.03
                capacidades: usb-2.00
                configuração: driver=hub slots=16 speed=480Mbit/s
              *-usb:0
                   descrição: Interface sem fio bluetooth
                   produto: JL AC69 A10
                   fabricante: Cambridge Silicon Radio, Ltd
                   ID físico: 1
                   informações do barramento: usb@1:1
                   versão: 25.20
                   capacidades: bluetooth usb-2.00
                   configuração: driver=btusb maxpower=100mA speed=12Mbit/s

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.3
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 12 09:18:43 2020
InstallationDate: Installed on 2019-06-19 (266 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: HP HP EliteDesk 800 G4 SFF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=885446d9-2945-4958-a7f0-1eadecf23697 ro locale=pt_BR quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q01 Ver. 02.06.03
dmi.board.name: 83E1
dmi.board.vendor: HP
dmi.board.version: KBC Version 07.D2.00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrQ01Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4SFF:pvr:rvnHP:rn83E1:rvrKBCVersion07.D2.00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.product.name: HP EliteDesk 800 G4 SFF
dmi.product.sku: 5ZA60LP#AC4
dmi.sys.vendor: HP

Revision history for this message
raimundoguimaraes1 (raimundoguimaraes1) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Which error is this bug about?

  Bluetooth: hci0: command 0x0c24 tx timeout

or

  Failed to add UUID: Busy (0x0a)

Separately, please note that Cambridge Silicon Radio dongles are known to be unreliable and cause bugs. Please try a different brand if you can.

affects: bluez (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
raimundoguimaraes1 (raimundoguimaraes1) wrote : Re: [Bug 1867147] Re: Failed to add UUID: Busy (0x0a)
Download full text (4.3 KiB)

I just want a driver to update the dongles.
The device works on ubuntu 16.04 only wanted the driver or settings that
works in the previous version
Awaiting return.

Em qui., 12 de mar. de 2020 às 22:45, Daniel van Vugt <
<email address hidden>> escreveu:

> Which error is this bug about?
>
> Bluetooth: hci0: command 0x0c24 tx timeout
>
> or
>
> Failed to add UUID: Busy (0x0a)
>
> Separately, please note that Cambridge Silicon Radio dongles are known
> to be unreliable and cause bugs. Please try a different brand if you
> can.
>
> ** Package changed: bluez (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867147
>
> Title:
> Failed to add UUID: Busy (0x0a)
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> dmesg
>
> Bluetooth: hci0: command 0x0c24 tx timeout
>
> rfkill list
>
> 0: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 1: hci1: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 2: phy0: Wireless LAN
> Soft blocked: yes
> Hard blocked: no
>
> bluetoothctl
>
> Failed to start discovery: org.bluez.Error.InProgress
>
>
> lsusb
>
> Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd
> Bluetooth Dongle (HCI mode)
>
> lshw
>
> *-usb
> descrição: USB controller
> produto: Cannon Lake PCH USB 3.1 xHCI Host Controller
> fabricante: Intel Corporation
> ID físico: 14
> informações do barramento: pci@0000:00:14.0
> versão: 10
> largura: 64 bits
> clock: 33MHz
> capacidades: pm msi xhci bus_master cap_list
> configuração: driver=xhci_hcd latency=0
> recursos: irq:124 memória:eb220000-eb22ffff
> *-usbhost:0
> produto: xHCI Host Controller
> fabricante: Linux 5.3.0-40-generic xhci-hcd
> ID físico: 0
> informações do barramento: usb@1
> nome lógico: usb1
> versão: 5.03
> capacidades: usb-2.00
> configuração: driver=hub slots=16 speed=480Mbit/s
> *-usb:0
> descrição: Interface sem fio bluetooth
> produto: JL AC69 A10
> fabricante: Cambridge Silicon Radio, Ltd
> ID físico: 1
> informações do barramento: usb@1:1
> versão: 25.20
> capacidades: bluetooth usb-2.00
> configuração: driver=btusb maxpower=100mA
> speed=12Mbit/s
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: bluez 5.48-0ubuntu3.3
> ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
> Uname: Linux 5.3.0-40-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7.11
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> ...

Read more...

Revision history for this message
raimundoguimaraes1 (raimundoguimaraes1) wrote :
Download full text (4.6 KiB)

or a link to the most up-to-date bluez package ... most current version for
Ubuntu 18.04 if any

Em sex, 13 de mar de 2020 13:37, raimundo guimaraes <
<email address hidden>> escreveu:

> I just want a driver to update the dongles.
> The device works on ubuntu 16.04 only wanted the driver or settings that
> works in the previous version
> Awaiting return.
>
> Em qui., 12 de mar. de 2020 às 22:45, Daniel van Vugt <
> <email address hidden>> escreveu:
>
>> Which error is this bug about?
>>
>> Bluetooth: hci0: command 0x0c24 tx timeout
>>
>> or
>>
>> Failed to add UUID: Busy (0x0a)
>>
>> Separately, please note that Cambridge Silicon Radio dongles are known
>> to be unreliable and cause bugs. Please try a different brand if you
>> can.
>>
>> ** Package changed: bluez (Ubuntu) => linux (Ubuntu)
>>
>> ** Changed in: linux (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1867147
>>
>> Title:
>> Failed to add UUID: Busy (0x0a)
>>
>> Status in linux package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> dmesg
>>
>> Bluetooth: hci0: command 0x0c24 tx timeout
>>
>> rfkill list
>>
>> 0: hci0: Bluetooth
>> Soft blocked: no
>> Hard blocked: no
>> 1: hci1: Bluetooth
>> Soft blocked: no
>> Hard blocked: no
>> 2: phy0: Wireless LAN
>> Soft blocked: yes
>> Hard blocked: no
>>
>> bluetoothctl
>>
>> Failed to start discovery: org.bluez.Error.InProgress
>>
>>
>> lsusb
>>
>> Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd
>> Bluetooth Dongle (HCI mode)
>>
>> lshw
>>
>> *-usb
>> descrição: USB controller
>> produto: Cannon Lake PCH USB 3.1 xHCI Host Controller
>> fabricante: Intel Corporation
>> ID físico: 14
>> informações do barramento: pci@0000:00:14.0
>> versão: 10
>> largura: 64 bits
>> clock: 33MHz
>> capacidades: pm msi xhci bus_master cap_list
>> configuração: driver=xhci_hcd latency=0
>> recursos: irq:124 memória:eb220000-eb22ffff
>> *-usbhost:0
>> produto: xHCI Host Controller
>> fabricante: Linux 5.3.0-40-generic xhci-hcd
>> ID físico: 0
>> informações do barramento: usb@1
>> nome lógico: usb1
>> versão: 5.03
>> capacidades: usb-2.00
>> configuração: driver=hub slots=16 speed=480Mbit/s
>> *-usb:0
>> descrição: Interface sem fio bluetooth
>> produto: JL AC69 A10
>> fabricante: Cambridge Silicon Radio, Ltd
>> ID físico: 1
>> informações do barramento: usb@1:1
>> versão: 25.20
>> capacidades: bluetooth usb-2.00
>> configuração: driver=btusb maxpower=100mA
>> speed=12Mbit/s
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu ...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Which error is this bug about?

  Bluetooth: hci0: command 0x0c24 tx timeout

or

  Failed to add UUID: Busy (0x0a)

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Guillaume Quittet (gquittet) wrote :

I have to same error with Ubuntu 20.10

Changed in linux (Ubuntu):
status: Expired → Confirmed
affects: linux (Ubuntu) → bluez (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Which error is this bug about?

  Bluetooth: hci0: command 0x0c24 tx timeout

or

  Failed to add UUID: Busy (0x0a)

Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
tags: added: groovy
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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