CSR8510 A10 [0a12:0001] Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) init failure: Connection timed out (110)

[pi0]

I own a USB Dongle 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). I am not able to scan devices. I plugged in the USB device in and out, restarted the my laptop, restarted the service and still will not be recognized by Wireshark or any other Bluetooth utility.

It worked perfectly with ubuntu 18.04 without any issues.

$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

hcitool dev
(the device is not listed)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: f00 1197 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 23:02:48 2020
InstallationDate: Installed on 2020-05-13 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. UX32A
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic N/A
 linux-firmware 1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.211:bd08/21/2012:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32A
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[pi0 (pizero)]

Hey Chris, of course.

I plugged in the USB Dongle CSR 4.0, attempted to scan my BT device, unfortunately my usb device was not recognized. I also wanted to use Wireshark with this dongle, but it was not detected as well.

I am able to use this device on Ubuntu 18.04 and scan my BT devices.

here is a description of

-------------------------------------------------------------------------------------

dmesg | grep -Ei 'blue|firm'

[ 0.134829] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.190638] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 3.176241] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x361f02)
[ 14.828855] iwlwifi 0000:02:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
[ 14.832704] Bluetooth: Core ver 2.22
[ 14.832723] Bluetooth: HCI device and connection manager initialized
[ 14.832727] Bluetooth: HCI socket layer initialized
[ 14.832729] Bluetooth: L2CAP socket layer initialized
[ 14.832732] Bluetooth: SCO socket layer initialized
[ 18.841575] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.841577] Bluetooth: BNEP filters: protocol multicast
[ 18.841582] Bluetooth: BNEP socket layer initialized
[ 21.640029] Bluetooth: RFCOMM TTY layer initialized
[ 21.640039] Bluetooth: RFCOMM socket layer initialized
[ 21.640045] Bluetooth: RFCOMM ver 1.11
[ 47.954359] Bluetooth: hci0: command 0x0c14 tx timeout
[ 231.120897] Bluetooth: hci0: command 0x0c14 tx timeout
[ 6942.437038] Bluetooth: hci0: command 0x0c14 tx timeout

-----------------------------------------------------------

$ sudo 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: no
 Hard blocked: no

[Kai-Heng Feng (kaihengfeng)]

There seems to be a builtin Intel Bluetooth controller, does it work?

[You-Sheng Yang (vicamo)]

https://bugzilla.kernel.org/show_bug.cgi?id=60824