Hi Alex, On Tue, Jun 25, 2013, Alex Deymo wrote: > I'm in 3.8.11 and I don't have that patch... and as I can see from the > log in mgmt.c it is not going to apply... there are already several > changes from this kernel to that point. But anyway... that won't fix > the problem. The scenario is "send a command, btmgmt power off, btmgmt > power on". The fact that the command was sent because a previous power > on is not relevant, and bluetoothd normally sends more commands when > it sees an interface going up that aren't covered by this lock (like > Write EIR, Write Class of Device, Write Local Name)... right? Not quite. What we do is program these values to the kernel as soon as we discover a new adapter and before powering it on. After this mgmt_set_powered takes care of actually "applying" the values as part of the power on process. The patch I mentioned should ensure that the kernel doesn't reply to the mgmt command before all of these HCI commands have completed. Of course this still doesn't fix the situation of an HCI command that's pending that's not part of the power on process (e.g. changing the name while powered on), so something will probably need to be done about that anyway. 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
