Re: [2.6.3] Mouse loosing sync (again)

[Kronos]

Il Fri, Feb 27, 2004 at 10:00:57PM +0100, Vojtech Pavlik ha scritto: 
> On Fri, Feb 27, 2004 at 09:14:41PM +0100, Kronos wrote:
> > Hi,
> > I still have troubles with mouse, it keeps jumping here and there and I
> > see lots of messages in logs:
> > 
> > Feb 27 20:49:55 dreamland kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> > Feb 27 20:50:42 dreamland kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
> > Feb 27 20:51:11 dreamland kernel: psmouse.c: bad data from KBC - bad parity
> > Feb 27 20:51:11 dreamland kernel: psmouse.c: bad data from KBC - bad parity
> > Feb 27 20:51:12 dreamland kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> > Feb 27 20:55:32 dreamland kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> > Feb 27 20:58:38 dreamland kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
> > 
> > These happened while surfing web with little activity on eth0 and while disks
> > were almost idle (-u1 is set on both of them). Using vmstat I see that
> > I'm getting around 1300 interrupts per second while moving mouse (less
> > than 1100 while doing nothing), so I don't think that there's something 
> > spinning in ISR for too long.
> > 
> > Problem first appeared in 2.6.2, 2.6.1 is unaffected. I see that in
> > 2.6.3 there's a patch which is supposed to fix this, but it still
> > happens for me.
> > 
> > Any clue?
> 
> The bad parity messages definitely suggest a problem with the mouse
> cable - either too long or broken.

Hum, but why does it work with older kernels? If I boot with 2.6.1 it
works without problems.

thanks,
Luca
-- 
Home: http://kronoz.cjb.net
Se non sei parte della soluzione, allora sei parte del problema.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/