public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Concannon <mike@concannon.net>
To: linux-kernel@vger.kernel.org
Subject: spurious mouse clicks
Date: Wed, 21 Sep 2005 09:49:40 -0400	[thread overview]
Message-ID: <433164F4.40205@concannon.net> (raw)

I thought it was my imagination at first, but now I have some slightly 
more convincing evidence of what is going on...

With 2.6.13.1 & 2 as I move my mouse around the screen, I get random 
clicks on things the mouse passes.  Seems to happen more often with the 
first move from idle, but in general, it is just totally random...

With 2.6.9-11.EL and 2.6.12.6 (stock kernel.org) I do NOT get this.

Anyone else seeing this?

I would blame the OS/WM/X, as I have recently upgraded to CentOS4, but 
now I have tried a few different kernels in the process of getting a 
stable config for my wireless setup and I am convinced that the only 
variable that seems to matter is the kernel version.  I have had this 
laptop for about a year and prior configs never had any mouse issues.

Config:
2.6.13.1 & 2 from kernel.org .config is the "default" from CentOS 4 - 
happy to post if anyone is interested.
Machine:
    Dell 8600 Pentium M 2GHz 1.5G ram
Mouse:
    touch pad PS/2 - dmesg/proc do not seem to show anything more 
specific than that
    PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
OS:
    CentOS 4.1 - KDE 3.3 stock config

/mike

             reply	other threads:[~2005-09-21 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 13:49 Michael Concannon [this message]
2005-09-21 14:08 ` spurious mouse clicks Tomasz Torcz
2005-09-21 14:16   ` Michael Concannon
2005-09-21 14:20     ` Michael Concannon
2005-09-21 19:51       ` Michael Concannon
2005-09-27 23:01         ` Michael Concannon

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=433164F4.40205@concannon.net \
    --to=mike@concannon.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