[Bug 2166119] Re: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71

Hey Leonardo, Thanks for submitting a bug report, and I'm glad to hear you were able to find a workaround. Has the USB bus been functioning normally since you did the Cold boot? For now I will mark this bug as Invalid, but if you find that the issue persists, please feel free to reopen it by setting the bug to "New" or "Confirmed". Thanks! ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166119 Title: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71 Status in linux package in Ubuntu: Invalid Bug description: Bluetooth worked normally on Ubuntu 24.04 LTS on this same laptop and hardware. After upgrading to Ubuntu 26.04 LTS, Bluetooth is no longer detected or available. Hardware: * ASUS VivoBook X512FB * Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter * PCI ID: 168c:0042 * Subsystem: Lite-On Communications Inc. 11ad:0836 * BIOS: X512FB.304 (08/26/2019) The Wi-Fi functionality of the QCA9377 continues to work normally. The Bluetooth controller is not detected: * `bluetoothctl list` returns no controller. * `lsusb` does not show a Bluetooth device. * No HCI device is present under `/sys/class/bluetooth`. * `rfkill` shows Bluetooth as unblocked. * `btusb` can be loaded successfully with `modprobe`, but no Bluetooth controller appears. The kernel log shows repeated USB enumeration failures on internal USB port 1-10: `usb 1-10: device descriptor read/64, error -110` followed by: `xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command` `usb 1-10: Device not responding to setup address.` `usb 1-10: device not accepting address 6, error -71` and finally: `usb usb1-port10: unable to enumerate USB device` The Bluetooth core and `btusb` driver are loaded, but no HCI controller is created because the underlying USB device fails to enumerate. The same laptop and QCA9377 hardware worked normally under Ubuntu 24.04 LTS. The Bluetooth problem appeared after upgrading to Ubuntu 26.04 LTS. This may be a kernel/USB/driver regression, as the same hardware worked normally on Ubuntu 24.04 LTS. However, I cannot confirm whether the issue is specifically a kernel regression yet. Expected behavior: The internal QCA9377 Bluetooth controller should be detected and available through `bluetoothctl`. Actual behavior: The Bluetooth controller fails USB enumeration with errors -110 and -71, no HCI controller is created, and Bluetooth is unavailable. Wi-Fi continues to work normally on the same QCA9377 adapter. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonardo 3444 F.... wireplumber /dev/snd/seq: leonardo 3433 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 19:26:53 2026 InstallationDate: Installed on 2026-08-28 (4 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:56d3 IMC Networks USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 006: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 006: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FB_X512FB ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=810b2ac5-8f88-4cc7-9814-dc3780fab91a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512FB.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512FB 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.:bvrX512FB.304:bd08/26/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FB_X512FB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBook: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512FB_X512FB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166119/+subscriptions