Messages in this thread | | | Date | Tue, 29 Jul 2003 23:32:28 -0700 | From | Andrew Morton <> | Subject | Re: another must-fix: major PS/2 mouse problem |
| |
Pavel Machek <pavel@ucw.cz> wrote: > > Hi! > > > > Loosing too many ticks! > > > TSC cannot be used as a timesource. (Are you running with SpeedStep?) > > > Falling back to a sane timesource. > > > psmouse.c: Lost synchronization, throwing 3 bytes away. > > > psmouse.c: Lost synchronization, throwing 1 bytes away. > > > > > > Arrrrgh! The TSC is my only good time source! > > > > Arrrgh! More PS/2 problems! > > > > I think the lost synchronisation is the problem, would you agree? > > > > The person who fixes this gets a Nobel prize. > > > If you set ps/2 synchronization timeout to 20 seconds, you are going to make vojtech > unhappy (he likes that code :-), but at least 2.6.0 will not be worse than 2.4.x...
2.6 is currently much worse than 2.4: we're buried in what appear to be many different varieties of PS/2 bug reports.
> Do you want me to create a patch?
Well I do not know what the problem with synchronisation is, not what solution you propose.
But yeah, I like patches ;)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |