Comment 6 for bug 1339249

The last time I got this error I spent about a day hacking around with random settings trying to get it to work, and I apparently fixed it but unfortunately I have no idea what I did to fix it.

I think it might have something to do with HCI usb, I remember messing around with those settings but again not sure what I did, this was 2 months ago. I believe I disabled HCI usb, and it may have taken a couple reboots to resolve the issue.

Some good news is I at least have some hints for you, I had saved all the different commands I was messing around with. But I'm not sure if the actual fix was in here as I could have done it in different terminal / tab.