Hi Marcel, >> Hi Steven, >> >>> I'm using bluez-5.35 with kernel 4.2 and am seeing that after a while (could be minutes, hours or days, I don't know what the trigger is) a BLE device will disconnect and the only way to reconnect to it is to rmmod the bluetooth modules and re-modprobe them. Obviously this shouldn't happen. I'm seeing the following output from bluetoothd (sorry for the huge log, let me know if a full pastebin would be better). Can anyone offer any insight into why once this happens, I can't talk to the device through Bluetooth? >> can you also show the btmon for this situation. And any chance to test 4.2.x stable kernel. A few patches went into stable kernel that might fix this. I would be also great if you can do a quick test with 4.3-rc7 and bluetooth-next kernels to see if this might be something that we already fixed. > The best I can do at the moment is 4.3-rc6 since this is running on an > ARM dev board that needs a special set of kernel patches. I've started > my program running on that and am running btmon as well. If the issue > happens again I'll post back with the btmon log. I have seen this again but the btmon log is quite long. Would you like me to send the whole thing to the list or would a pastebin work better? Does the list have a preference as to which? Thanks Steven Davies -- 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
