Can kernel parameter "usbcore.enable_autosuspend=0" workaround the issue?
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
