From: Dmitry Torokhov <dtor_core@ameritech.net>
To: bhaskara <bhaskara@aludra.usc.edu>
Cc: Voluspa <lista1@telia.com>, linux-kernel@vger.kernel.org
Subject: Re: mouse still losing sync and thus jumping around
Date: Mon, 13 Jun 2005 17:03:06 -0500 [thread overview]
Message-ID: <200506131703.07315.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.GSO.4.33.0506131450100.21818-100000@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.
--
Dmitry
next prev parent reply other threads:[~2005-06-13 23:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 21:40 mouse still losing sync and thus jumping around Voluspa
2005-06-13 21:47 ` Dmitry Torokhov
2005-06-13 23:45 ` Voluspa
2005-06-13 21:59 ` bhaskara
2005-06-13 22:03 ` Dmitry Torokhov [this message]
2005-06-13 22:22 ` bhaskara
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 14:21 Bennie Kahler-Venter
2005-03-21 22:22 ` Andrew Morton
2005-05-25 22:07 ` Andrew Morton
2005-05-26 8:19 ` Bennie Kahler-Venter
2005-05-27 12:58 ` Bennie Kahler-Venter
2005-05-27 13:57 ` Dmitry Torokhov
2005-02-23 13:22 Nils Kalchhauser
2005-02-23 14:17 ` Dmitry Torokhov
2005-02-23 16:29 ` Nils Kalchhauser
2005-02-23 16:53 ` Dmitry Torokhov
2005-02-24 3:05 ` Anthony DiSante
2005-02-24 3:18 ` Dmitry Torokhov
2005-02-24 8:16 ` Anthony DiSante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506131703.07315.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=bhaskara@aludra.usc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox