https://bugzilla.kernel.org/show_bug.cgi?id=104011 Robert R. Howell <rhowell@xxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rhowell@xxxxxxxx --- Comment #2 from Robert R. Howell <rhowell@xxxxxxxx> --- I've tried testing the patch in above attachment 186691 (using the 4.2 kernel, an ASUS T100, and a Logitech MX Anywhere 2 mouse) and unfortunately it produces the same "Bluetooth: SMP security requested but not available" error. As an experiment I tried reverting the original Aug. 15 patch which introduced the check for chan == 0 . With that test removed I get an immediate, complete lock-up of the machine when I try to connect to the mouse, presumably when l2cap_chan_lock is called with the null value. So it appears that check is needed, and it must be some earlier kernel change which first broke access to the mouse. I can't narrow down the origin of the problem better than your report that kernel 4.1.6 version worked, but I did test the T100 with an old 3.16.0 kernel and the mouse did work with it, so this isn't a hardware problem. I've done less extensive tests on a different (ASUS G750) machine and the mouse works with kernel 4.0-rc6 but fails with 4.2. Unfortunately my system isn't set up to easily bisect where the problem actually began. -- 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
