Re: mouse still losing sync and thus jumping around

[bhaskara <bhaskara@aludra.usc.edu>]

> On Monday 13 June 2005 16:59, bhaskara wrote:
> > > On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
> > > > On Wed, 23 Feb 2005 17:29:49 +0100, Nils Kalchhauser wrote:
> > > [...]
> > > >> it seems to me like it is connected to disk activity... is that
> > > >> possible?
> > >
> > > > Yes, It usually happens either under high load, when mouse interrupts
> > > > are significantly delayed. Or sometimes it happen when applications
> > > > poll battey status and on some boxes it takes pretty long time. And
> > > > because it is usually the same chip that serves keyboard/mouse it
> > > > again delays mouse interrupts.
> > >
> > > My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
> > > model: 1, fw: 5.8, id: 0x9248b1, caps: 0x904713/0x4000
> > >
> > > Kernels 2.6.11.11 and 2.6.12-rc6
> > > Synaptics driver 0.14.2
> > >
> > > The "lost sync at byte" and "driver resynched" began flooding the logs
> > > when I enabled Sensors --> Temperatures --> thermal_zone [THRC/THRS] in
> > > the system monitor gkrellm. I haven't tried battery monitoring.
> > >
> > > There are only occasional mouse pointer jumps, but the logfiles grow
> > > very quickly. I tried reducing the gkrellm updates from 10 times a
> > > second to 2, but it only had a marginal effect. It seems a bit silly
> > > that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask'
> > > correctly.
> > >
> > > I thought about just erasing the warning messages from the kernel
> > > source (don't want to disable warn in syslog completely), but when I
> > > found the gkrellm culprit I turned off the monitoring instead,
> > > reluctantly.
> > >
> > > My system has no taxing desktop, just a window manager.
> > >
> >
> > I had this problem with the ps2 mouse on my desktop even under very light
> > load. This problem went away the very instant I started using a USB mouse.
> > So, I don't buy the delayed interrupts explanation.
> >
>
> You do not have to buy anything, you just need to read the code. pmouse
> driver emits this warning if delay between 2 bytes in a middle of a packet
> exceeds 0.5 sec. USB works slightly differently.

No offense ..... but, I did some googling and figured out where the mesg
was being printed from. So I ripped out all the unnecessary stuff from the
kernel and also stopped all the unnecessary services, but still got this
behavior (with XFCE and KDE). By the way , my desktop
started exhibiting this behaviour after  a couple of months of usage and
not immediately after a kernel upgrade (2.6.8+).  However, I remember not
seeing this behavior on older 2.6.* kernels.

The .5 second delay is a symptom rather than the cause ( bad hardware ? ).

-G

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