From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: akpm@digeo.com
Subject: another must-fix: major PS/2 mouse problem
Date: Sat, 31 May 2003 21:46:03 -0400 [thread overview]
Message-ID: <1054431962.22103.744.camel@cube> (raw)
Lots of people (check Google) get this message
from the kernel:
psmouse.c: Lost synchronization, throwing 2 bytes away.
(the number of bytes will be 1, 2, or 3)
At work, I get it when there is heavy NFS traffic.
The mouse goes crazy, jumping around and doing
random cut-and-paste all over everything. This is
with a decently fast and modern PC.
I'll guess that NFS and the mouse both have worker
threads fighting for CPU time, and neither is RT.
next reply other threads:[~2003-06-01 1:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 1:46 Albert Cahalan [this message]
2003-06-04 5:47 ` another must-fix: major PS/2 mouse problem Yoann
[not found] ` <20030603232155.1488c02f.akpm@digeo.com>
2003-06-04 7:47 ` Vojtech Pavlik
2003-06-04 7:53 ` Andrew Morton
2003-06-04 8:00 ` Vojtech Pavlik
2003-06-04 8:14 ` Andrew Morton
2003-06-04 8:40 ` Vojtech Pavlik
2003-06-04 19:20 ` Yoann
2003-06-04 23:09 ` Albert Cahalan
[not found] ` <3EDCF47A.1060605@ifrance.com>
[not found] ` <1054681254.22103.3750.camel@cube>
[not found] ` <3EDD8850.9060808@ifrance.com>
2003-07-23 0:44 ` Albert Cahalan
2003-07-24 17:30 ` Andrew Morton
2003-07-25 1:46 ` Albert Cahalan
2003-07-26 3:19 ` Andrew Morton
2003-07-26 15:16 ` Zwane Mwaikambo
2003-07-29 2:55 ` Albert Cahalan
2003-07-29 3:14 ` Andrew Morton
2003-07-29 12:40 ` Albert Cahalan
2003-07-29 18:58 ` Andrew Morton
2003-07-29 19:36 ` Zwane Mwaikambo
2003-07-29 19:43 ` Chris Friesen
2003-07-30 5:08 ` Pavel Machek
2003-07-30 6:32 ` Andrew Morton
2003-07-30 12:29 ` Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 19:18 Mikael Pettersson
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=1054431962.22103.744.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@digeo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.