Hi Mark, >> Took me a while to figure out you have to bring down the hci0 interface and >> stop bluetoothd before running bluemoon. Otherwise I get "Failed to open >> HCI user channel." So now when I run bluemoon -T it just sits there forever >> after the welcome message. Is this expected behavior? Should I then >> restart bluetoothd in another console and leave the whole thing for a couple >> of days to catch the USB disconnect? > > Ok, I think I am seeing a bug very similar to this one reported by Loic > Poulain: > > http://marc.info/?l=linux-bluetooth&m=143220351521634&w=2 > ("bluetooth-next HCI user channel issue") > > I have the same symptom of bluemoon hanging, and I figured out that I can > recover the system without rebooting by forcing hci0 down again. "hciconfig > hci0 down" takes about ten seconds to return, and then I have a 0xfc3f > timeout in dmesg: > > [ 5563.562554] Bluetooth: hci0 command 0xfc3f tx timeout > [ 5571.557618] Bluetooth: hci0: turning off Intel device LED failed (-110) > > This is the same error Loic was getting, I assume because the commit in > question has now made it into my kernel (4.2.0-rc4). there are patches in 4.2-rc8 at least that should avoid this issue in combination with HCI User Channel. If this is still an issue, then we need to fix this. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
