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

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

[Simon Gate]

Changed from kernel 2.6.1 to 2.6.2 an get this error in dmesg

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

My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?

Best regards
++ Simon

*--- -  -
|  Simon Gate
|  simon@noir.se
*-  - 

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[Michael Buesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 14 February 2004 22:43, you wrote:
> Changed from kernel 2.6.1 to 2.6.2 an get this error in dmesg
> 
> psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> 
> My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?

here's the fix:

- --- linux-2.6.3-rc2/drivers/input/serio/i8042.c.orig	2004-02-10 21:33:21.000000000 +0100
+++ linux-2.6.3-rc2/drivers/input/serio/i8042.c	2004-02-10 21:37:03.000000000 +0100
@@ -379,6 +379,8 @@
 	unsigned int dfl;
 	int ret;
 
+	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
+
 	spin_lock_irqsave(&i8042_lock, flags);
 	str = i8042_read_status();
 	if (str & I8042_STR_OBF)
@@ -433,7 +435,6 @@
 irq_ret:
 	ret = 1;
 out:
- -	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
 	return IRQ_RETVAL(ret);
 }
 

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALppFFGK1OIvVOP4RAtHeAKDWzyU7PgdkwhhYrY3t+Zvqmv4aagCdHbNv
VUwVin8INy2JiK9+x6VMFr0=
=qV4u
-----END PGP SIGNATURE-----

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[Vojtech Pavlik]

On Sat, Feb 14, 2004 at 10:59:26PM +0100, Michael Buesch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Saturday 14 February 2004 22:43, you wrote:
> > Changed from kernel 2.6.1 to 2.6.2 an get this error in dmesg
> > 
> > psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> > 
> > My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?
> 
> here's the fix:

... no, that's a fix for a different bug. Actually, without this fix it
works more or less OK.

> - --- linux-2.6.3-rc2/drivers/input/serio/i8042.c.orig	2004-02-10 21:33:21.000000000 +0100
> +++ linux-2.6.3-rc2/drivers/input/serio/i8042.c	2004-02-10 21:37:03.000000000 +0100
> @@ -379,6 +379,8 @@
>  	unsigned int dfl;
>  	int ret;
>  
> +	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
> +
>  	spin_lock_irqsave(&i8042_lock, flags);
>  	str = i8042_read_status();
>  	if (str & I8042_STR_OBF)
> @@ -433,7 +435,6 @@
>  irq_ret:
>  	ret = 1;
>  out:
> - -	mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
>  	return IRQ_RETVAL(ret);
>  }

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[Ricky Beam]

On Sat, 14 Feb 2004, Michael Buesch wrote:
>> psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
>>
>> My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?

I've seen this junk for many years.  It's not limited to just 2.6.

In my current environment, it's the KVM screwing with the mouse data...
somehow it starts passing through 3 byte commands when the mouse is in
4 byte mode.  I fixed it by a little trickery to force the mouse to
reset (not a simple task from the ISR :-)  BTW, 250ms is WAY to long to
wait to detect a lose of sync; mice don't pause at all between bytes.)

>here's the fix:
...

And exactly what is that supposed to be fixing?

--Ricky

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[Vojtech Pavlik]

On Mon, Feb 16, 2004 at 03:58:20PM -0500, Ricky Beam wrote:

> On Sat, 14 Feb 2004, Michael Buesch wrote:
> >> psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> >>
> >> My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?
> 
> I've seen this junk for many years.  It's not limited to just 2.6.
> 
> In my current environment, it's the KVM screwing with the mouse data...
> somehow it starts passing through 3 byte commands when the mouse is in
> 4 byte mode.  I fixed it by a little trickery to force the mouse to
> reset (not a simple task from the ISR :-)  BTW, 250ms is WAY to long to
> wait to detect a lose of sync; mice don't pause at all between bytes.)

Mice don't, but the kernel does, like when it's accessing the harddrive
heavily.

> >here's the fix:
> ...
> 
> And exactly what is that supposed to be fixing?
> 
> --Ricky
 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[Vojtech Pavlik]

On Sat, Feb 14, 2004 at 10:43:48PM +0100, Simon Gate wrote:
> Changed from kernel 2.6.1 to 2.6.2 an get this error in dmesg
> 
> psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> 
> My mouse goes crazy for a few secs and then returns to normal for a while. Is this a 2.6.2 problem or is this is something old?

It's a 2.6.2 bug and fixed in 2.6.3-rc1.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

[aeriksson]

Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Sat, Feb 14, 2004 at 10:43:48PM +0100, Simon Gate wrote:
> > Changed from kernel 2.6.1 to 2.6.2 an get this error in dmesg
> > 
> > psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 
> bytes away.
> > 
> > My mouse goes crazy for a few secs and then returns to normal for a while. 
> Is this a 2.6.2 problem or is this is something old?
> 
> It's a 2.6.2 bug and fixed in 2.6.3-rc1.
> 

Just switched to 2.6.3 and I can report that this misbehavior is still
there. Not quite as frequent as before (just a feeling). There seems
to be another failure mode introduced now. At time it just freezes for
about 1-3 seconds. I.e. The mouse just don't respond to anything. The
crazy movements are the more common failure mode though.

Anyone else recognize this? I get the infamous "psmouse.c: Wheel Mouse
at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away."
thing still...

suggestions are welcome...

/Anders