From: Pavel Machek <pavel@ucw.cz>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: psmouse synchronization loss under load
Date: Mon, 22 Dec 2003 13:32:37 -0500 [thread overview]
Message-ID: <20031222183237.GA15844@openzaurus.ucw.cz> (raw)
In-Reply-To: <20031220015131.GB9834@vitelus.com>
Hi!
> On a Dell laptop whenever I run a program that takes the full CPU, my
> mouse pointer goes insane and thrashes my X session every few minutes.
> It seems to have a mind of its own and always be able to make it to
> the Exit item in the root menu ;). Whenever this happens, psmouse logs
> and detects the error:
>
> psmouse.c: Mouse at isa0060/serio4/input0 lost synchronization, throwing
> 2 bytes away.
Do you use ACPI? Using APM made the error go away for me.
next prev parent reply other threads:[~2004-01-12 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 1:51 psmouse synchronization loss under load Aaron Lehmann
2003-12-20 2:26 ` Bernd Eckenfels
2003-12-20 4:01 ` Dmitry Torokhov
2003-12-20 3:49 ` Dmitry Torokhov
2003-12-22 18:32 ` Pavel Machek [this message]
2004-01-13 0:54 ` Aaron Lehmann
-- strict thread matches above, loose matches on Subject: below --
2004-01-09 13:30 Moritz Moeller-Herrmann
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=20031222183237.GA15844@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
/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