Hi Tore, On Thu, Mar 03, 2016, Tore Anderson wrote: > > One thing you could still try is use an even newer kernel, such as the > > bluetooth-next tree or the latest 4.5-rc release, and see if the issue > > still persists. > > I did with fresh git pulls: > > bluetooth-next @ 9dbadc0: Works > linux (torvalds) @ f983cd3: Broken > > If you'd like I can try to bisect it this weekend to figure out exactly > where it got fixed, if not I'll just content myself with the knowledge > that it'll probably get fixed in the mainline kernel eventually. It's a relief to hear that the issue seems to be fixed, but it would indeed be good to get to the bottom of this and understand what exactly fixed it, since I can't right now remember any recent patches that would have influenced this behavior (who knows - maybe it's something external to the Bluetooth subsystem). Johan -- 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
