From: Mark Lord <lkml@rtr.ca>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
rubini@vision.unipv.it, linux-input@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: 2.6.24: false double-clicks from USB mouse
Date: Sun, 02 Dec 2007 13:52:46 -0500 [thread overview]
Message-ID: <4752FEFE.3000600@rtr.ca> (raw)
In-Reply-To: <4752FE11.2050200@rtr.ca>
Mark Lord wrote:
>
> Here's a *single* button click (press/release quickly):
>
> Event: time 1196621063.612542, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1196621063.612553, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1196621063.620504, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1196621063.620512, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1196621063.628497, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1196621063.628502, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1196621063.684524, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1196621063.684531, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1196621063.700532, type 1 (Key), code 272 (LeftBtn), value 1
> Event: time 1196621063.700538, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1196621063.764540, type 1 (Key), code 272 (LeftBtn), value 0
> Event: time 1196621063.764550, type 0 (Reset), code 0 (Reset), value 0
..
Note that, much of the time, a single mouse click looks like this:
Event: time 1196621357.073485, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1196621357.073494, type 0 (Reset), code 0 (Reset), value 0
Event: time 1196621357.201482, type 1 (Key), code 272 (LeftBtn), value 0
Event: time 1196621357.201492, type 0 (Reset), code 0 (Reset), value 0
So the first one I posted was probably the same kind of sequence
that leads to the unwanted double-clicks I'm reporting here.
This information may also be relevant:
The mouse is plugged into a USB2 hub, and appears as IRQ19:
19: 34776 0 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5
Cheers
next prev parent reply other threads:[~2007-12-02 18:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 16:21 2.6.24: false double-clicks from USB mouse Mark Lord
2007-12-02 16:21 ` Mark Lord
2007-12-02 16:58 ` Mark Lord
2007-12-02 16:58 ` Mark Lord
2007-12-02 17:04 ` REGRESSION: " Mark Lord
2007-12-02 17:04 ` Mark Lord
2007-12-02 17:07 ` Arjan van de Ven
2007-12-02 17:07 ` Arjan van de Ven
2007-12-02 17:14 ` Mark Lord
2007-12-02 17:14 ` Mark Lord
2007-12-02 17:57 ` Jeff Garzik
2007-12-02 17:57 ` Jeff Garzik
2007-12-02 18:09 ` Jiri Kosina
2007-12-02 18:09 ` Jiri Kosina
2007-12-06 8:27 ` Diego Zuccato
2007-12-06 8:27 ` Diego Zuccato
2007-12-06 12:21 ` Jiri Kosina
2007-12-06 12:21 ` Jiri Kosina
2007-12-02 18:07 ` Jiri Kosina
2007-12-02 18:17 ` Mark Lord
2007-12-02 18:20 ` Mark Lord
2007-12-02 18:23 ` Jiri Kosina
2007-12-02 18:48 ` Mark Lord
2007-12-02 18:52 ` Mark Lord [this message]
2007-12-02 19:09 ` Jiri Kosina
2007-12-02 19:24 ` Mark Lord
2007-12-02 19:27 ` Jiri Kosina
2007-12-02 19:44 ` Mark Lord
2007-12-02 22:07 ` Jiri Kosina
2007-12-02 22:46 ` Mark Lord
2007-12-07 17:59 ` Ray Lee
2007-12-07 17:59 ` Ray Lee
2007-12-07 18:32 ` Dmitry Torokhov
2007-12-07 18:32 ` Dmitry Torokhov
2007-12-07 21:23 ` Ray Lee
2007-12-07 21:43 ` Dmitry Torokhov
2007-12-02 18:06 ` Oliver Neukum
2007-12-02 18:06 ` Oliver Neukum
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=4752FEFE.3000600@rtr.ca \
--to=lkml@rtr.ca \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@garzik.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@vision.unipv.it \
/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.