Bluetooth unavailable after updates - Reading Intel version information failed (-110)

[Redsandro]

After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available.

$ dmesg | grep -i bluetooth
[ 4.846072] Bluetooth: Core ver 2.22
[ 4.846088] Bluetooth: HCI device and connection manager initialized
[ 4.846092] Bluetooth: HCI socket layer initialized
[ 4.846094] Bluetooth: L2CAP socket layer initialized
[ 4.846096] Bluetooth: SCO socket layer initialized
[ 5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.434082] Bluetooth: BNEP filters: protocol multicast
[ 5.434086] Bluetooth: BNEP socket layer initialized
[ 6.874125] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6.874129] Bluetooth: hci0: Reading Intel version information failed (-110)

$ uname -a
Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS.

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1859592

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.

[Redsandro (redsandro)]

I read from previous bugs and forums on the internet that people seem to think this is BIOS _update_ related. Things don't just break from one day to the next because you suddenly need a firmware update. I tried a couple of things like going to BIOS and loading default settings. Save. Reboot. No change.

What finally DID resolve the problem was removing the power cable for a couple of seconds and putting it back in.

So although this issue can be closed, I have this deja vu that this kind of weird bluetooth issue happens once or twice per year, but only with Linux. Either this is a coincidence, or there is some kind of state, signal, message, or bit that Windows does or does not send, as opposed to Linux.

[Terry Rudd (terrykrudd)]

thanks for following up on this

[Hosup choi (tervancovan)]

Thank you Terry
Your soloution was perfect

[heheman3000 (mizzao)]

I also had this issue, which first manifested by bluetoothd being completely unresponsive and being unkillable, even with SIGKILL. The whole system would lag at regular intervals.

After a hot reboot (no power cycle), the lag went away but it was impossible to activate bluetooth and dmesg showed the same messages as above:

Bluetooth: hci0: command 0xfc05 tx timeout
Bluetooth: hci0: Reading Intel version information failed

Finally after a cold power off and then back on, everything started working again. So it would seem that there is actually some hardware bug here, because the issue persists across reboots if the bluetooth chip is not power cycled.

[Redsandro (redsandro)]

@mizzao that sounds a lot like my "solution" comments/2 indeed. However, during hot reboots on my dual boot setup, the Bluetooth DID work in Windows for me, but not in Linux. For Linux, a cold boot was required.

So I am inclined to believe that the Linux Bluetooth driver puts the Bluetooth hardware in a certain state that persists across hot reboots but doesn't affect the Windows driver from successfully interacting with the Bluetooth hardware.

I believe this to be a software bug where a certain state or signal from the Bluetooth hardware is misinterpreted by the Linux driver, causing it to stop working.

[You-Sheng Yang (vicamo)]

Please do run `apport-collect 1859592` after a cold boot to submit logs because Intel bluetooth may only reload fwd after that, and only when it probes fw we may know its hw variant.

[Redsandro (redsandro)]

@vicamo any cold boot, right? Not specifically after having this error?

For the moment I'm working at home because of reasons, but one of these weeks I'll be at the office (computer) again. But the error itself is pretty rare.

I'm also encouraging @mizzao to `apport-collect 1859592`

[Ian Morris (lawsonim1)]

I too am having this problem after a suspend/resume [deep].

Kubuntu 18.04 (nearly up to date patches (20200424)

dmesg:

[285163.220315] Bluetooth: hci0: command 0xfc05 tx timeout
[285163.220316] Bluetooth: hci0: Reading Intel version information failed (-110)

To restart the BT adapter a simple:-

rmmod btusb
rmmod btintel
modprobe btinel
modprobe btusb

is sufficient for me.

I hope this helps.

[You-Sheng Yang (vicamo)]

@Redsandro, any cold boot and only cold boot will Intel reload fw and print fw filename. We know it rarely happens, and that's why we're eager to know what hardware variant do you have.

@Ian, you can modprobe btusb alone and it will also load btintel as well. ~lazy engineer.

[Martin Wickman (martin-wickman)]

@vicamo I'm experiencing this as well. Ie. only a cold boot will fix it.

Is there anything I can do to help debug this?

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/

[Yash Murty (yashmurty)]

For me as well, the power cable did the trick. Thank you!
As mentioned in this comment above:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2

[Ray (passionfruit)]

I also encountered this issue, with ubuntu 18.04 and intel AX200NGW Bluetooth. Would be willing to help provide debugging logs if needed.

[Martin Wickman (martin-wickman)]

I'm happy to report that it seems to work with kernel mainline 5.7. I do get the error, but it works without having to cold boot the system at least.

5.7.14-050714-generic #202008070831 SMP Fri Aug 7 08:34:53 UTC 2020

[ 5.291451] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[ 5.291474] ucsi_ccg 0-0008: i2c_transfer failed -110
[ 5.291490] ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
[ 5.291514] ucsi_ccg: probe of 0-0008 failed with error -110
[ 5.410031] kauditd_printk_skb: 35 callbacks suppressed
[ 6.339748] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6.339765] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 6.339783] Bluetooth: hci0: Intel Read version failed (-110)
[ 6.339807] Bluetooth: hci0: Intel reset sent to retry FW download
[ 6.960249] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 6.961209] Bluetooth: hci0: Device revision is 2
[ 6.961209] Bluetooth: hci0: Secure boot is enabled
[ 6.961210] Bluetooth: hci0: OTP lock is enabled
[ 6.961210] Bluetooth: hci0: API lock is enabled
[ 6.961210] Bluetooth: hci0: Debug lock is disabled
[ 6.961211] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.969280] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 8.650286] Bluetooth: hci0: Waiting for firmware download to complete
[ 8.651210] Bluetooth: hci0: Firmware loaded in 1652098 usecs
[ 8.651287] Bluetooth: hci0: Waiting for device to boot
[ 8.664214] Bluetooth: hci0: Device booted in 12689 usecs
[ 8.667041] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[ 8.670247] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 8.672259] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[ 17.041132] Bluetooth: RFCOMM TTY layer initialized
[ 17.041136] Bluetooth: RFCOMM socket layer initialized
[ 17.041139] Bluetooth: RFCOMM ver 1.11

[Quaylyn Rimer (killerdevildog11)]

I came here from this link https://askubuntu.com/questions/1231074/ubuntu-20-04-bluetooth-not-working/1237801 cold rebooting from windows then booting back into Ubuntu fixed the problem. is there any update on fixing the switching in between Windows and Ubuntu while using Bluetooth devices?

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Patrick Kusebauch (patrick-kusebauch)]

If there is a need for additional debug info, this bug is currently affecting me and I am free to provide any logs neccessary.

[Alex Burdu (alex.burdu)]

Cold boot as in powering off from PC's source button worked (taking electricity off the mother board) worked for me.

Just shutting down and having the motherboard LEDs on didn't work.

[Diego Lineros (diegolineros)]

Hi, can someone help... Cold boot is not working for me!!!!!!!!!!!! I am getting Failed to send firmware data (-38)

$ dmesg | grep -i bluetooth
[ 5.985839] Bluetooth: Core ver 2.22
[ 5.985858] Bluetooth: HCI device and connection manager initialized
[ 5.985864] Bluetooth: HCI socket layer initialized
[ 5.985867] Bluetooth: L2CAP socket layer initialized
[ 5.985872] Bluetooth: SCO socket layer initialized
[ 6.132508] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 6.138629] Bluetooth: hci0: Device revision is 5
[ 6.138631] Bluetooth: hci0: Secure boot is enabled
[ 6.138631] Bluetooth: hci0: OTP lock is enabled
[ 6.138632] Bluetooth: hci0: API lock is enabled
[ 6.138632] Bluetooth: hci0: Debug lock is disabled
[ 6.138633] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.183029] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 6.206658] Bluetooth: hci0: Failed to send firmware data (-38)
[ 6.206731] Bluetooth: hci0: Intel reset sent to retry FW download
[ 8.736500] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.736503] Bluetooth: BNEP filters: protocol multicast
[ 8.736512] Bluetooth: BNEP socket layer initialized
$ lspci -knn | grep Net -A3;lsusb
02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
 Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

[Michael K. (surfer298)]

I had the same problem after a suspend/resume cycle => bluetooth was not working with the message `hci0: Reading Intel version information failed (-110)` in the syslog.
For me the kernel parameter `btusb.enable_autosuspend=0` fixed this problem.

[Christopher Hill (brother-seal)]

I've also had this issue - twice - caused by leaving my desktop in standby for > 24hrs (can't say the exact duration). Cold booting after ensuring residual current has been expelled from the system has fixed it on both occasions.

It sounds like #1905214. My hardware is also

Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

I will try the kernel parameter `btusb.enable_autosuspend=0` but (touch wood) won't be able to replicate for another week as this system is my daily-driver.

[Raviteja (rlokineni)]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ravi 2111 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
HibernationDevice: RESUME=UUID=bf502ad2-5020-47f3-a3a0-2e011dbd9a88
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 5986:066d Acer, Inc BisonCam, NB Pro
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System76, Inc. Gazelle
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-7614-generic root=UUID=aa81a262-e1fc-4aa7-90ab-d27bdc57f96d ro acpi_backlight=vendor quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.10~ecb25cd~dev-generic 5.11.13
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-7614-generic N/A
 linux-backports-modules-5.11.0-7614-generic N/A
 linux-firmware 1.196+system76~1617760239~20.10~be8660e~dev
Tags: groovy
Uname: Linux 5.11.0-7614-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.08RSA1-1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Gazelle
dmi.board.vendor: System76, Inc.
dmi.board.version: gaze10
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.08RSA1-1:bd03/31/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze10:rvnSystem76,Inc.:rnGazelle:rvrgaze10:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Gazelle
dmi.product.sku: Not Applicable
dmi.product.version: gaze10
dmi.sys.vendor: System76, Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2016-03-01T13:52:38.380000

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Raviteja (rlokineni)]

apport information

[Kai-Heng Feng (kaihengfeng)]

This patch may help, please give it a try:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8bf7111b4bda00ae82e2de0cd871af997c3f2e9b

[Gustavo A. Díaz (gdiaz)]

Hi,

I am having the same issue, with a TP Link Archer Tx50e (which uses Intel AX200). On boot logs:

[ 8.084096] Bluetooth: hci0: command 0xfc05 tx timeout
[ 8.084101] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 8.084110] Bluetooth: hci0: Intel Read version failed (-110)

The workaround I use for this to make it work after my computer boot:

sudo modprobe -r btusb && sudo modprobe btusb

Ubuntu: 20.04
Kernel: 5.11.0-27-generic

Is there a fix for this? Thanks.

[Abdelrhman Gad (abdelrhmangad7197)]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gad 1821 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:64d2 Microdia Integrated Webcam
 Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 5880
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E5570
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=fc8f615e-1d7e-4e0a-a8ce-a0655746f51c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-40-generic N/A
 linux-backports-modules-5.11.0-40-generic N/A
 linux-firmware 1.197.3
Tags: wayland-session hirsute
Uname: Linux 5.11.0-40-generic x86_64
UpgradeStatus: Upgraded to hirsute on 2021-07-16 (124 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/02/2019
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.6
dmi.board.name: 0N98Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:br1.21:svnDellInc.:pnLatitudeE5570:pvr:sku06DF:rvnDellInc.:rn0N98Y6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E5570
dmi.product.sku: 06DF
dmi.sys.vendor: Dell Inc.

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[Abdelrhman Gad (abdelrhmangad7197)]

apport information

[David Nunez (arizonatribe)]

Also had an issue with Bluetooth (Fedora): GUI says it was off but "systemctl status bluetooth" says it is enabled, active, and running. Found this thread after running "dmesg" and finding that same error: "Reading Intel version information failed".

Pulling out the power cable (while the machine was running) fixed the issue for me as well. Tried a dozen or so things before, but nothing else worked. Thanks for the suggestion!

[Rashmitha (rashmitha)]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rashmitha 1751 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-08-24 (140 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera
 Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 250 G7 Notebook PC
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=c2e675a6-0a05-4eab-90f2-87dc5a7dd094 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-46-generic N/A
 linux-backports-modules-5.11.0-46-generic N/A
 linux-firmware 1.187.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.11.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo ubridge
_MarkForUpload: True
dmi.bios.date: 08/31/2021
dmi.bios.release: 15.38
dmi.bios.vendor: Insyde
dmi.bios.version: F.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8533
dmi.board.vendor: HP
dmi.board.version: 70.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 70.38
dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:sku6YE09PA#ACJ:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 250 G7 Notebook PC
dmi.product.sku: 6YE09PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Rashmitha (rashmitha)]

apport information

[Angel Parrales (angelparrales)]

Power cable unplug as comment #2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2 did the trick

[Cory Gugler (cory-gugler)]

Power cable unplug also did the trick for me.

[Ching-Hsiang Kuo (asika3rd)]

Power cable unplug saved my day too.

[Cody Cutrer (ccutrer)]

I encountered this after upgrading to Jammy from Focal. Power cable unplug also fixed it for me.

[Jeroen (c0p3rn1c)]

My bluetooth stopped working after updates installed on 27-09-2022. (I've set my system to do daily automatic updates and use my system every day)

dmesg errors:
[ 439.808973] Bluetooth: hci0: command 0xfc05 tx timeout
[ 439.808993] Bluetooth: hci0: Reading Intel version command failed (-110)

I tried the workaround above:
rmmod btusb
rmmod btintel
modprobe btinel
modprobe btusb

Error message:
modprobe: FATAL: Module btinel not found in directory /lib/modules/5.15.0-48-generic

uname -a
Linux jeroen-G14 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

sudo dmesg | grep -i blue
[ 13.175035] Bluetooth: Core ver 2.22
[ 13.175244] NET: Registered PF_BLUETOOTH protocol family
[ 13.175247] Bluetooth: HCI device and connection manager initialized
[ 13.175252] Bluetooth: HCI socket layer initialized
[ 13.175255] Bluetooth: L2CAP socket layer initialized
[ 13.175261] Bluetooth: SCO socket layer initialized
[ 13.973399] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.973405] Bluetooth: BNEP filters: protocol multicast
[ 13.973412] Bluetooth: BNEP socket layer initialized
[ 15.264704] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 15.264718] Bluetooth: hci0: command 0xfc05 tx timeout
[ 439.808973] Bluetooth: hci0: command 0xfc05 tx timeout
[ 439.808993] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 690.984174] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 690.986189] Bluetooth: hci0: Device revision is 1
[ 690.986194] Bluetooth: hci0: Secure boot is enabled
[ 690.986196] Bluetooth: hci0: OTP lock is enabled
[ 690.986197] Bluetooth: hci0: API lock is enabled
[ 690.986198] Bluetooth: hci0: Debug lock is disabled
[ 690.986198] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 690.990251] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 692.814237] Bluetooth: hci0: Waiting for firmware download to complete
[ 692.815153] Bluetooth: hci0: Firmware loaded in 1782123 usecs
[ 692.815289] Bluetooth: hci0: Waiting for device to boot
[ 692.830194] Bluetooth: hci0: Device booted in 14621 usecs
[ 692.835981] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[ 692.842248] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 692.851533] Bluetooth: hci0: Firmware revision 0.3 build 126 week 5 2022
[ 693.053456] Bluetooth: RFCOMM TTY layer initialized
[ 693.053473] Bluetooth: RFCOMM socket layer initialized
[ 693.053483] Bluetooth: RFCOMM ver 1.11

[Jeroen (c0p3rn1c)]

That workaround fixed it (after a while?)

[Sergei (olosegres)]

Power cable unplug is not OK workaround.

Please somebody who know how and can do it:
- create bug report to the kernel project
- or create a fix to the kernel (to the hci_core.c ?)

[David Farrell (dnmfarrell)]

I have this issue after suspend/resume on Ubuntu 20.04 LTS, kernel 5.15.0, Dell Precision 5540 with an Intel Core i9-9980HK processor.

lsusb shows the device:
Bus 001 Device 025: ID 8087:0029 Intel Corp

Which is an Intel AX200 Bluetooth wireless chip.

Suspending and resuming my laptop once more fixes the issue. No need to cold reboot. Here is the Bluetooth dmesg output from this morning's suspend/resume cycles:

[58674.253723] Bluetooth: hci0: command 0xfc05 tx timeout
[58674.253724] Bluetooth: hci0: Reading Intel version command failed (-110)
[58795.067813] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[58795.068737] Bluetooth: hci0: Device revision is 1
[58795.068739] Bluetooth: hci0: Secure boot is enabled
[58795.068740] Bluetooth: hci0: OTP lock is enabled
[58795.068741] Bluetooth: hci0: API lock is enabled
[58795.068741] Bluetooth: hci0: Debug lock is disabled
[58795.068742] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[58795.068952] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[58796.844050] Bluetooth: hci0: Waiting for firmware download to complete
[58796.844645] Bluetooth: hci0: Firmware loaded in 1734054 usecs
[58796.844836] Bluetooth: hci0: Waiting for device to boot
[58796.859635] Bluetooth: hci0: Device booted in 14567 usecs
[58796.859721] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[58796.861740] Bluetooth: hci0: Applying Intel DDC parameters completed
[58796.864875] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[58796.924662] Bluetooth: hci0: MSFT filter_enable is already on

[Bhalchandra Pandit (bhalchandrap)]

I used to get the following error after each reboot. That started happening after the most recent Ubuntu 20.04 update.

Bluetooth: hci0: command 0xfc05 tx timeout
Bluetooth: hci0: Reading Intel version command failed (-110)

I verified that the following workaround works for me. Thankfully, it does not involve pulling out the power plug.

First verify that your device is reported as DOWN.

~ $ hciconfig
hci0: Type: Primary Bus: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:4 acl:0 sco:0 commands:1 errors:0

If so, run the following command:

~ $ sudo hciconfig -a hci0 up

and then reboot normally. I was able to use Bluetooth normally after that step.

[xh (imagineb)]

I get this bug =too

[xh (imagineb)]

I get this bug too

[MisterSheeple (mistersheeple)]

I also had this bug. The workaround posted in November helped fix it for me.