Description of problem: Once switched on, bluetooth repeatedly switches on and off again. I'm running Fedora 21 (beta) with all updates applied (as of 2014-11-18). Kernel version 3.17.3-300.fc21.x86_64. The report from dmesg is [ 2743.244014] usb 1-1.6: new full-speed USB device number 110 using ehci-pci [ 2743.334358] usb 1-1.6: New USB device found, idVendor=0930, idProduct=0213 [ 2743.334366] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2743.334370] usb 1-1.6: Product: BRCM Bluetooth Controller BCM2070 [ 2743.334375] usb 1-1.6: Manufacturer: Broadcom Corp [ 2743.334378] usb 1-1.6: SerialNumber: 4CEDDE03953D [ 2745.429025] toshiba_bluetooth: Re-enabling Toshiba Bluetooth [ 2745.626831] usb 1-1.6: USB disconnect, device number 110 [ 2745.864280] usb 1-1.6: new full-speed USB device number 111 using ehci-pci [ 2745.987728] usb 1-1.6: New USB device found, idVendor=0930, idProduct=0213 which repeats continuously. I ended up having to blacklist the toshiba_bluetooth module which obviously renders bluetooth inoperable. How reproducible: Steps to Reproduce: 1. Turn on bluetooth 2. Turn on feature to receive files (may not be necessary)
I have a similar issue with a new Toshiba laptop. It will only happen when bluetooth is turned OFF, and regardless of the distro (Redhat, Arch, Debian...) and desktop environment (Gnome 3, Xfce). Basically, toshiba_bluetooth keeps switching the device on and off continuosly, filling the logs like this: http://pastebin.com/npcBtHZY Steps to reproduce: 1. Turn off bluetooth 2. Check dmesg
No reply, no updates... is there any chance of seeing a fix for this?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The bug has been reported upstream and a patch has been provided. If you are a Toshiba user please help test it, info and patched module available at https://bugzilla.kernel.org/show_bug.cgi?id=93911