public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Gustafsson <andersg@0x63.nu>
To: Joshua Kwan <joshk@ludicrus.ath.cx>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [2.5.54-dj1-bk] Some interesting experiences...
Date: Wed, 8 Jan 2003 02:51:07 +0100	[thread overview]
Message-ID: <20030108015107.GA2170@gagarin> (raw)
In-Reply-To: <20030107172147.3c53efa8.joshk@ludicrus.ath.cx>

On Tue, Jan 07, 2003 at 05:21:46PM -0800, Joshua Kwan wrote:
> 
> 3. [linux-2.5] PS/2 mouse goes haywire every 30 seconds or so of use.
> dmesg sayeth:
> mice: PS/2 mouse device common for all mice
> input: PS/2 Synaptics TouchPad on isa0060/serio4
> 
> but more importantly this is the cause:
> 
> psmouse.c: Lost synchronization, throwing 2 bytes away.
> psmouse.c: Lost synchronization, throwing 2 bytes away.

This happens here too. But not that frequent at all, more like once every
hour. And has happend on all kernels since at least 2.5.46 [1].

However 5 hours ago I changed the timeout in psmouse.c from 50ms to 100ms.
And now it haven't misbehaved yet, but that might be just some nightly luck. 
Is there something that turns off interupts or something and hinders the
mouse driver from processing the data for such long time? Or is my hardware
just buggy?

[1] http://marc.theaimsgroup.com/?l=linux-kernel&m=103688231622278&w=2

-- 
Anders Gustafsson - andersg@0x63.nu - http://0x63.nu/

  reply	other threads:[~2003-01-08  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  1:21 [2.5.54-dj1-bk] Some interesting experiences Joshua Kwan
2003-01-08  1:51 ` Anders Gustafsson [this message]
2003-01-08  8:52   ` Vojtech Pavlik
2003-01-09 20:04     ` Anders Gustafsson
2003-01-09 21:02       ` Joshua Kwan
2003-01-08  1:58 ` dhinds
2003-01-08  4:43   ` Joshua Kwan
2003-01-08  5:56     ` Joshua Kwan
2003-01-08  6:16       ` dhinds

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=20030108015107.GA2170@gagarin \
    --to=andersg@0x63.nu \
    --cc=joshk@ludicrus.ath.cx \
    --cc=linux-kernel@vger.kernel.org \
    --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