From: Jamie Lokier <jamie@shareable.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Murilo Pontes <murilo_pontes@yahoo.com.br>, linux-kernel@vger.kernel.org
Subject: Re: psmouse.c, throwing 3 bytes away
Date: Sat, 7 Feb 2004 02:35:10 +0000 [thread overview]
Message-ID: <20040207023510.GI12503@mail.shareable.org> (raw)
In-Reply-To: <20040205203840.GA13114@ucw.cz>
Vojtech Pavlik wrote:
> On Thu, Feb 05, 2004 at 05:24:27PM +0000, Murilo Pontes wrote:
> > I try kernel with/without preempty/acpi/apic make all possibilities,
> > then may be error is not in kernel, but in XFree86-4.3.0 which not support big changes in input system
> > of 2.6.x, I tried compile XFree86 with linux-2.6.{0,1,2} kernel headers was 100% fail, sounds binary
> > and source incompatibilites,
>
> Hey, guys, could you possibly try to figure out what your machines have
> in common? I've switched all my computers to PS/2 mice so that I have a
> bigger chance to reproduce the problem, but it is not happening on any
> of them.
Heh. I have a USB mouse and I see similar problems:
Red Hat 9 (more or less), XFree86-4.3.0-2, kernel 2.6.0-test10, dual
athlon, USB Logitech optical mouse, configured to read from
/dev/input/mice (only!).
Every few hours the mouse suddenly jumps to a corner of the screen and
seems broken for a second or so. After that I can move it back to
where it is useful.
I never noticed such behaviour when running 2.4 on this box, nor when
running earlier 2.6 kernels.
There is nothing about "atkbd" or "mouse" or "lost synchronisation" in
the kernel log.
-- Jamie
next prev parent reply other threads:[~2004-02-07 2:35 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 2:20 psmouse.c, throwing 3 bytes away Walt Nelson
2004-02-05 4:54 ` Claudio Martins
2004-02-05 10:20 ` Isaac Claymore
2004-02-09 6:15 ` Isaac Claymore
2004-02-09 9:09 ` Vojtech Pavlik
2004-02-09 9:49 ` Isaac Claymore
2004-02-09 9:52 ` Vojtech Pavlik
2004-02-05 13:40 ` Michael Buesch
2004-02-05 15:31 ` johann lombardi
2004-02-05 5:05 ` Mike Houston
2004-02-05 17:24 ` Murilo Pontes
2004-02-05 20:38 ` Vojtech Pavlik
2004-02-05 18:14 ` Murilo Pontes
2004-02-05 19:08 ` Murilo Pontes
2004-02-05 21:06 ` Michael Buesch
2004-02-05 22:10 ` Mike Houston
2004-02-06 7:15 ` Mike Houston
2004-02-06 8:06 ` Walt Nelson
2004-02-07 5:47 ` Mike Houston
2004-02-07 9:11 ` Murilo Pontes
2004-02-08 21:59 ` Vojtech Pavlik
2004-02-08 22:19 ` aeriksson
2004-02-08 22:32 ` Vojtech Pavlik
2004-02-08 23:03 ` Bernd Schubert
2004-02-08 23:30 ` Vojtech Pavlik
[not found] ` <40278077.5070409@free.fr>
2004-02-09 22:25 ` Bernd Schubert
2004-02-09 0:48 ` [patch] " Vojtech Pavlik
2004-02-09 1:13 ` Claudio Martins
2004-02-09 1:23 ` Vojtech Pavlik
2004-02-10 2:56 ` Greg Norris
2004-02-10 7:07 ` Vojtech Pavlik
2004-02-10 7:39 ` Walt Nelson
2004-02-10 19:48 ` Greg Norris
2004-02-10 20:08 ` Vojtech Pavlik
2004-02-10 7:33 ` johann lombardi
2004-02-10 21:11 ` Murilo Pontes
2004-02-11 4:44 ` Claudio Martins
2004-02-06 0:33 ` Pete Clements
2004-02-06 22:44 ` Kronos
2004-02-07 2:35 ` Jamie Lokier [this message]
2004-02-07 4:19 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 6:18 Bob Gill
2004-02-05 21:56 Luis Miguel García
2004-02-05 19:33 ` Murilo Pontes
2004-02-06 7:02 ` Claudio Martins
2004-02-06 10:12 ` Christian Unger
2004-02-06 17:52 ` Adrian Bunk
2004-02-06 18:03 ` Michael Buesch
2004-02-06 21:49 ` Claudio Martins
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=20040207023510.GI12503@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murilo_pontes@yahoo.com.br \
--cc=vojtech@suse.cz \
/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