Comment 8 for bug 85247

I've got the same issue with Feisty and the 2.6.20-16 kernel. After connecting the dongle and waiting a bit and then a disconnect the output from dmesg is:

[ 74.449625] Bluetooth: HCI device and connection manager initialized
[ 74.449632] Bluetooth: HCI socket layer initialized
[ 74.578322] Bluetooth: L2CAP ver 2.8
[ 74.578333] Bluetooth: L2CAP socket layer initialized
[ 74.624702] Bluetooth: RFCOMM socket layer initialized
[ 74.624733] Bluetooth: RFCOMM TTY layer initialized
[ 74.624737] Bluetooth: RFCOMM ver 1.8
[ 126.955108] usb 1-1: new full speed USB device using uhci_hcd and address 3
[ 127.106230] usb 1-1: configuration #1 chosen from 1 choice
[ 127.571169] Bluetooth: HCI USB driver ver 2.9
[ 127.572593] usbcore: registered new interface driver hci_usb
[ 127.614522] Bluetooth: Broadcom Blutonium firmware driver ver 1.1
[ 127.694143] usbcore: registered new interface driver bcm203x
[ 148.526188] bcm203x_complete: URB failed with status -84
[ 148.632436] usb 1-1: USB disconnect, address 3

I backported the driver from 2.6.18 as Adam suggested and then dropped the bcm module (without the custom kernel) into the standard kernel directory and the dongle comes up fine.

I noticed that the state of this bug is 'Needs info'. If you can let me know what you need (maybe I just missed it above) I can try to provide the data.