public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Concannon <mike@concannon.net>
To: Michael Concannon <mike@concannon.net>
Cc: Tomasz Torcz <zdzichu@irc.pl>, linux-kernel@vger.kernel.org
Subject: Re: spurious mouse clicks
Date: Wed, 21 Sep 2005 15:51:12 -0400	[thread overview]
Message-ID: <4331B9B0.6050300@concannon.net> (raw)
In-Reply-To: <43316C36.1010703@concannon.net>

Michael Concannon wrote:

> Michael Concannon wrote:
>
>> Tomasz Torcz wrote:
>>
>>>>
>>>> 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.
>>>>
>>> Do you have lines like:
>>>
>>> psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost 
>>> synchronization, throwing 1 bytes away.
>>>
>>> in your dmesg?
>>>
>> [mike@porthos proc]$ dmesg | grep -i throwing
>> [mike@porthos proc]$ dmesg | grep -i psmouse
>>
>> it would appear not...
>
>
> oops - I am running 2.6.12.6 now - I guess I should try the offending 
> kernel before I answer that question ;-)
>
> BTW - I also neglected to mention that I routinely lower Hz to 250 in 
> param.h to remove sound-card whine - but I did this with all kernels 
> in question... (it is now a CONFIG option in 2.6.13 which is nice... )

Been using 2.6.13.2 most of the day - and though I have seen fewer 
random clicks - I am still seeing them...

no dmesg output though...  anything else I can check?

Thanks,

/mike


  reply	other threads:[~2005-09-21 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 13:49 spurious mouse clicks Michael Concannon
2005-09-21 14:08 ` Tomasz Torcz
2005-09-21 14:16   ` Michael Concannon
2005-09-21 14:20     ` Michael Concannon
2005-09-21 19:51       ` Michael Concannon [this message]
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=4331B9B0.6050300@concannon.net \
    --to=mike@concannon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zdzichu@irc.pl \
    /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