Comment 61 for bug 717970

@jm-leddy: I tested the patch by patching and rebuilding [1] the actual Raring kernel (3.8.0.-25.37). To my mind, no improvement compared to the non-patchted kernel, which means if the touchpad lost sync and stops working it takes a long time to reconnect. Of course I also get the output [2].

Imho, best experience is using Kernel 3.10rc7 mainline, which I am testing currently. There, I can still reproduce (heavy typing during using the touchpad) the lost syncs with non-working touchpad but the time to reconnect is quite low. Maybe it's due to Ubuntu's patch [3] which got finally mainlined in 3.10 [4], maybe it's something different. I will use and test 3.10 in the next few days, maybe the time window to reconnect is small enough that the user does not recognize it. But as I said the output and non-working can still be triggered with my touchpad [5].

[1] https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

[2] psmouse serio4: issuing reconnect request
 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
 psmouse serio4: issuing reconnect request

[3] http://thread.gmane.org/gmane.linux.kernel.input/25599

[4] https://bugzilla.kernel.org/process_bug.cgi

[5] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd047b3/0xb40000/0xa0000, board id: 71, fw id: 578367