mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Daniel Mierswa <impulze@impulze.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gericom Webboy Laptop Mouse/Touchpad
Date: Tue, 31 Jul 2007 23:26:06 +0200	[thread overview]
Message-ID: <20070731212606.GA3643@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <46AF935B.9020403@impulze.org>

Hi,

On Tue, Jul 31, 2007 at 09:54:03PM +0200, Daniel Mierswa wrote:
> 
> Hi there,
> i'm having troubles getting my mouse and/or touchpad to work with 
> 2.6.21.5 (and older ones). It's putting the following line into dmesg 
> everytime the laptop gets lots of I/O or cpu load.
> "psmouse.c: Wheel Mouse at isa0060/serio4/input0 lost synchronization, 
> throwing 2 bytes away."

This message is a wee bit too familiar to me as well, albeit for reasons
different to that, I believe. :-$

> The problem still exists and seems to occur as i've mentioned on lots of 
> disk i/o and/or cpu load.
> This is a laptop which is not supported by the manufactur anymore (seems 
> to be a Gericom Webboy). I would appreciate any tips to debug this further.
> Please post back for any additional information you need.

Hmm, I'm pondering what I'd do here...
Could it be that you're using the "old" IDE layer (not libata yet) and
hdparm -u or -d or -c is inconveniently set up?

Maybe run powertop to identify timer anomalies?
Try configuring a different CONFIG_HZ?
Or maybe run oprofile to try to figure out any abnormal system load?
And did you try running a "barebone"-only configuration? Possibly some
certain driver is causing this misbehaviour...
vmstat may provide some initial information as to what kind of activity
exactly causes this issue.

Or maybe it's a simple X.org scheduling issue again?
What nice value do you run X.org at?
If it's too low, then maybe this causes the psmouse.c driver to have its
mouse queue(?) processing get stuck and makes it have a hickup?
In this context it would be good to ask about possible memory pressure on
this system, too, since recently some people indicated more fluid X.org mouse
pointer operation when mlocking the pointer handling code to avoid
paging this code.

Oh, given that IIRC the Webboy is a slightly older Gericom model which
thus may easily be a (somewhat hotter) P4 *desktop* CPU: could it be that
you're hitting thermal emergency throttling on increased system activity?
cat /proc/acpi/processor/*/throttling or something there might indicate
this.

HTH,

Andreas Mohr

  reply	other threads:[~2007-07-31 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 19:54 Daniel Mierswa
2007-07-31 21:26 ` Andreas Mohr [this message]
2007-08-01 19:26 Daniel Mierswa

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=20070731212606.GA3643@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=impulze@impulze.org \
    --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®