Comment 78 for bug 268502

The configuration menu only lets you select one of the two drivers, but I don't see a reason the two should conflict as long as you only allow one of them to load.

Switching to the older driver is more of a workaround than a solution. The new driver needs to be fixed one way or another, and once we have the fix, we can backport it.

But anyone who wants working Bluetooth today can build a custom kernel with hci_usb instead of btusb.