Re: 2.6.x atkbd.c moaning

From: Michael Frank
Date: Thu Mar 18 2004 - 14:21:39 EST


On Fri, 19 Mar 2004 01:03:38 +0800, Michael Frank <mhf@xxxxxxxxxxxxx> wrote:

On Thu, 18 Mar 2004 23:01:14 +1100, Anton Blanchard <anton@xxxxxxxxx> wrote:


Why is this and should I investigate further?
..

mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).

Did this happen recently? If so, does backing out the following patch help?

I think so but later than this changeset 1.34 of 19 December.

The Unknown key release msg is introduced in 2.6.1 with i8042 changesets from 1.33 to 1.35
(likely 1.34 as Anton suggested). Guess i did not think much of it as it was "smaller"
but "blaming xfree" during boot since 2.6.2 caught my attention.


The patch has no effect.

Also the mouse screws up after a few hours and becomes unusable.
On 2.6.4

On 2.6.[012] the mouse does not sync at all (even after power up).

On 2.4.18-26 mouse never had problems.


psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.

Could also be load dependent. Will do more testing on 2.6.4 to reproduce.

The serious issue with the mouse is that it does not recover and stays
out of sync and interprets further movement as random coordinates/button clicks.

x2x mouse works.

Regards
Michael


-
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/