https://bugzilla.kernel.org/show_bug.cgi?id=104011 --- Comment #4 from Robert R. Howell <rhowell@xxxxxxxx> --- Further testing reveals that the situation is more complicated than I described above, because it depends upon the past pairing history with the mouse. What I described above is correct if I remove the pairing with the device, then try to redo the pairing from scratch with the above patched kernels. However I get different results if a leave a previous "legacy" pairing in place. I've discovered that I can boot an "old enough" kernel (3.16.0 and probably 4.0-rc6) and successfully pair with and use the mouse. If I then reboot into a 4.2 kernel using either the above attachment 186691 patch or one where I simply revert the Aug. 14 (and it was Aug. 14, not 15) patch, then I do NOT get the SMP warning and the mouse works correctly. If I boot the 4.2 kernel WITH the Aug. 14 patch, I DO get the SMP warning and the mouse fails. So it looks like there are two different but related problems. The practical effect of the Aug. 14 patch is to forbid "legacy" pairings and the 186691 attachment removes that legacy prohibition in a crash-proof way. Unfortunately there is some additional but perhaps related bug which prevents the 4.2 kernel and either modified version from successfully creating a new "correct" pairing with the mouse. When, under 4.2 with or without the 186691 patch, I remove any legacy pairing then use bluetoothctl to try to establish a new pairing, the "pair command SAYS it completes successfully, but it triggers the SMP error message viewable with with dmesg. Although later "connect" commands sometimes SAY they succeed (they are not consistent), the mouse is never usable. As mentioned earlier, if I try to create a new pairing after removing the Aug. 14 patch entirely, then the system locks up immediately. At this point I've probably reached the limits of my understanding of the bluetooth system, but if others have patches, I'd be happy to test them. -- You are receiving this mail because: You are the assignee for the bug. -- 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
