Created attachment 21360 [details] changes to get the mx900 working correctly Here is a good description of the issue http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518467 basically instead of moving smoothly the mouse stutters around as if the computer is not receiving all of the packets Works fine in 2.6.25 but was broken in 2.6.27 (still broken in 2.6.30-rc5), therefore, I did a git bisect start -- net/bluetooth git bisect bad v2.6.27 git bisect good v2.6.25 and eventually it winded down to the bad commit at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e4e8e37c42bdaaefcb84eeaef0dc1bc3f696f8f6 So I tried undoing a couple of the changes and narrowed it down to a few places (attached in mx900.patch), which basically undoes the commit's purpose - therefore it was only for my use to narrow down where the breakage occurred (and to have my mouse work in the mean time)
Created attachment 21361 [details] log of the mouse working correctly this is a log of the mouse working correctly, I used the dynamic debug with bluetooth, hci, and hidp modules set to log, and it was taken from dmesg
Created attachment 21362 [details] log of the mouse not working properly this is a log of the mouse not working properly, used dynamic debug with the modules bluetooth, hci, and hidp to set to log, taken from dmesg
Created attachment 21363 [details] lsudb of the bluetooth module in the computer lsudb of the bluetooth module in the computer
thanks for taking a look
Thanks, but we're poorly set up for handling, reviewing and merging patches via bugzilla. Could you please formulate this report and description as a patch and email it to linux-bluetooth@vger.kernel.org linux-kernel@vger.kernel.org Andrew Morton <akpm@linux-foundation.org> (it doesn't matter if the patch is "wrong" - it gives me something to hang onto so the issue doesn't get forgotten) ?
yup I can do that, it may be a while because I have to review patch submission guidelines, but I will definitely do it
Hi, Any news about this patch? My bluetooth mouse is also affected by http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e4e8e37c42bdaaefcb84eeaef0dc1bc3f696f8f6 change. I have reverted that change in my 2.6.30.2 kernel and my mouse (0458:0058) works well now.
I've got the same mouse as previous poster, and can confirm that the problem is still present in 2.6.31.
Closing as obsolete, if present versus a recent kernel please re-open