From: fire-eyes <sgtphou@fire-eyes.dynup.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.2: psmouse.c: .... Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Date: Sun, 08 Feb 2004 01:18:39 -0500 [thread overview]
Message-ID: <4025D4BF.7010309@fire-eyes.dynup.net> (raw)
Please CC: me, as I am not subscribed to this list.
I am using kernel 2.6.2 with SMP support on an Asus A7M-266D
motherboard. I am using a Logitech M-BJ69 ps/2 mouse.
While in xfree, twice today I had the following happen:
While using the mouse, the pointer suddenly jumped wildly all over the
place, I heard exactly two PC speaker beeps, then I got control back.
This took about a quarter second in total. After that, no mouse button
worked, including wheels.
I ctl-alt-backspace out of xfree. I check my load and it is high. I'm
using xfce 4.0.3 window manager, and xfwm4 is taking up 99.9% of cpu. I
need to kill -9 it. Not sure if xfce4 is actually a problem, I don't see
how it would affect the mouse.
Both times I got the following error in logs:
kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost
synchronization, throwing 3 bytes away.
Here is some more info on my system:
Gentoo Linux
glibc-2.3.3_pre20040117
gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)
xfree 4.3.99.902
Now what stands out there is the xfree version. I never had this error
in 4.3.0.
Starting xfree and xfce4, I get the following in logs. And yes it really
is this many times:
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Is there any further info I can provide to help solve a possible problem?
Thanks!
next reply other threads:[~2004-02-08 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 6:18 fire-eyes [this message]
2004-02-08 9:00 ` Murilo Pontes
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=4025D4BF.7010309@fire-eyes.dynup.net \
--to=sgtphou@fire-eyes.dynup.net \
--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
all inboxes | Powered by JetHome®