On Tuesday 01 February 2005 00:06, Pete Zaitcev wrote: > On Mon, 31 Jan 2005 22:40:35 -0500, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > > > > Suddenly, touchpad motions started to cause wild movements in it became > > > impossible to do anything due to a focus loss (of course, I had plenty of > > > modified files open :-) > > > > psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3 > > > psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched. > > > psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 3 > > > psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > > > psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > > > psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched. > > > 1. Have you tried using external PS/2 mouse? > > 2. Have you plugged/unplugged into a port replicator? > > I have Dell Latitude D600, which does not have an external PS/2 port. > > But actually, I was caught away from home, working from a library, so I did > not have either PS/2 or USB mouse. I moved the cursor persistently for a > few minutes until I managed to raise a window in such way that it got the > focus, then I saved all files and closed all windows from the keyboard, > so no harm done, no problem. > > The kernel was running without resetafter set, unfortunately. > > If you have a patch which prints offending data from pktbuffer, I can > run that next time. >
No I don't but by the looks of it (constant stream of bad data) it looks like somehow the touhcpad was reset back into PS/2 compatibility mode. resetafter would catch it and reinitialize touchpad restoring proper protocol. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/