Red Hat Bugzilla – Bug 1248447
Bluetooth fails after suspend and resume
Last modified: 2016-07-19 13:16:02 EDT
Description of problem:
I am running Fedora 22 on a DELL XPS 13 (2015 model, bios A04). When I first installed Fedora I followed the instructions available at
to install the bluetooth driver. After I upgraded to kernel 4.1.2-200.fc22.x86_64 I started having problems connecting my bluetooth devices (mice) after a suspend (to RAM) and resume.
With previous kernels (4.0), after suspend and resume sometimes my bluetooth mouse was laggy and erratic. I then pressed Fn + PrtScr twice and it would get back to normal. Alternatively, I could do
sudo modprobe -r btusb
sudo modprobe btusb
However, after I upgraded to kernel 4.1 bluetooth simply does not work after a few suspend and resume.
Version-Release number of selected component (if applicable):
Fedora 22, bluez 5.29-2.
Quite reproducible, I believe.
Steps to Reproduce:
1. Suspend to RAM
3. Try to connect a bluetooth device (for example, a mouse)
Unable to connect bluetooth devices.
Bluetooth devices should connect after a suspend and resume.
[13767.880493] usb 1-3: USB disconnect, device number 2
[13767.924270] dell_wmi: Unknown key 153 pressed
[13768.581447] ERROR @wl_notify_scan_status : wlp2s0 Scan_results error (-22)
[13770.358140] dell_wmi: Unknown key 153 pressed
[13770.581687] usb 1-3: new full-speed USB device number 5 using xhci_hcd
[13770.748150] usb 1-3: New USB device found, idVendor=0a5c, idProduct=216f
[13770.748153] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[13770.748154] usb 1-3: Product: BCM20702A0
[13770.748155] usb 1-3: Manufacturer: Broadcom Corp
[13770.748156] usb 1-3: SerialNumber: ACD1B8C06F5C
[13770.754593] Bluetooth: hci0: BCM: chip id 63
[13770.755597] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[13770.755617] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-216f.hcd failed with error -2
[13770.755620] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-216f.hcd not found
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.