--- Begin Message ---
Package:linux-image-2.6.12-1-686
Version:2.6.12-10
This is an intermittent bug that has just got worse. I have a Toshiba
Portege 7020CT with a builtin trackpoint and a PS/2 mouse that I
connect via the PS/2 port in a port extension. The trackpoint is
working fine but the PS/2 mouse behaves strangely (moves at random,
gives out random mouse click events) and I get this in my kern.log:
Nov 9 17:45:49 portege kernel: psmouse.c: Mouse at
isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
I have "psmouse proto=bare" in my /etc/modules, and have tried the
solutions suggested at
http://www.kerneltraffic.org/kernel-traffic/kt20040212_252.html,
including stopping apmd. I also have speedstep_lib in my /etc/modules.
Any other info on request.
Cheers
David
--- End Message ---
--- Begin Message ---
- To: 338347-done@bugs.debian.org
- Subject: Re: Bug#338347: psmouse driver keeps losing synchronization
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Sat, 18 Jul 2009 00:22:33 +0200
- Message-id: <20090717222233.GA1935@galadriel.inutil.org>
- In-reply-to: <20081226104143.GA5458@galadriel.inutil.org>
- References: <20080514072302.GB10689@stro.at> <20081226104143.GA5458@galadriel.inutil.org>
On Fri, Dec 26, 2008 at 11:41:43AM +0100, Moritz Muehlenhoff wrote:
> On Wed, May 14, 2008 at 09:23:02AM +0200, maximilian attems wrote:
> > > The only way I seem to be able to fix is: stop apmd; modprobe -r
> > > psmouse; unplug mouse; plug mouse back in; modprobe psmouse. That
> > > works some of the time. (Stopping apmd may not be necessary, I am not
> > > sure.)
> > >
> > > David
> >
> > hello david,
> >
> > sorry for coming back that late, could you give an update on a recent
> > kernel aka >= 2.6.24.
> > is the 2.6.12 and 2.6.14 trouble still reproducible?
>
> David,
> does this error still occur with more recent kernel versions?
>
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html
This bug report has been pinged at least twice for more
information, so I'm closing it now.
If anyone reenconters the problem, please reopen this
bug.
Cheers,
Moritz
--- End Message ---