From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: touchpad stuck sometimes
Date: Mon, 10 Aug 2009 10:23:22 +0200 [thread overview]
Message-ID: <5a4c581d0908100123t7d68c751kfb4f70d68852e2cb@mail.gmail.com> (raw)
In-Reply-To: <a8e1da0908072003j1267ec89p366dc62c271663b7@mail.gmail.com>
On Sat, Aug 8, 2009 at 5:03 AM, Dave Young <hidave.darkstar@gmail.com> wrote:
>
> On Sun, Aug 2, 2009 at 4:16 PM, Dave Young<hidave.darkstar@gmail.com> wrote:
> > Hi,
> >
> > My touchpad sometimes will stuck for a while, and then it will be ok.
> >
> > I can see kernel message like this:
> >
> > [ 1293.426227] psmouse.c: GlidePoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
> > [ 1293.969357] psmouse.c: resync failed, issuing reconnect request
> >
> > Hardware is dell e5400, kernel version: 2.6.31-rc5
> >
> > --
> > Regards
> > dave
> >
[apologies for the dup, my GMail compose window was somehow
stuck on HTML and the vger lists bounced my message - here
it is in plain text]
Sort of a "me too" - on my Dell E6400 I get the touchpad stuck or not
moving correctly (almost stuck, or way too fast) - in those cases it's
enough to take fingers off touchpad and use the stick for a second,
everything resumes its normal operation.
I have these in the logs, not sure it's the same issue as the one I am
describing, but likely the same as Dave's submission:
2.6.31-rc3-git2:
Jul 22 11:04:51 duff kernel: 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Jul 22 12:03:28 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Jul 22 12:03:28 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Jul 22 12:03:28 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Jul 22 12:03:28 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 - driver resynched.
2.6.31-rc5-git3:
Aug 7 10:12:01 duff nm-system-settings: ifcfg-rh: read
connection 'System eth0'
Aug 7 16:42:29 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Aug 7 16:42:29 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 - driver resynched.
Aug 7 16:42:29 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Aug 7 16:42:29 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 lost sync at byte 1
Aug 7 16:42:29 duff kernel: psmouse.c: DualPoint TouchPad at
isa0060/serio1/input0 - driver resynched.
cheers,
--alessandro
"And if a God will lay to rest anywhere we want to go
In your house I long to be, room by room, patiently"
(Audioslave, "Like A Stone")
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-08-10 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 8:16 touchpad stuck sometimes Dave Young
2009-08-08 3:03 ` Dave Young
2009-08-10 8:23 ` Alessandro Suardi [this message]
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=5a4c581d0908100123t7d68c751kfb4f70d68852e2cb@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).