From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Damjan Jovanovic <damjan.jov@gmail.com>,
linux-input@vger.kernel.org, Arvind K <arvindkhadri@gmail.com>,
Peter Hutterer <peter.hutterer@who-t.net>
Subject: Re: psmouse: "bad data from KBD - bad parity" every 2ms with synaptics touchpad
Date: Tue, 1 Nov 2011 23:00:12 -0700 [thread overview]
Message-ID: <20111102060012.GB29035@core.coreip.homeip.net> (raw)
In-Reply-To: <20111101193458.GA10933@elie.hsd1.il.comcast.net>
On Tue, Nov 01, 2011 at 02:34:58PM -0500, Jonathan Nieder wrote:
> Damjan Jovanovic wrote:
>
> > Maybe that touchpad doesn't send proper parity. See what we did in commit
> > 6b9d363c49d22395d0cf8729c5963f83cfbb6d69, and try to disable parity
> > checking for that touchpad the same way?
>
> Sure, though it would be nice to understand the problem better first.
>
> So:
>
> - Arvind, could you say a little more about when this started
> happening[1]? Did you change your configuration, or was there any
> upgrade around the same time (/var/log/dpkg.log* should say)? Any
> idea why this wasn't always happening from the start?
If this was working and then stopped I'd try removing the keyboard and
cleaning and reseating the touchpad connector.
>
> - Others, any idea what information would be useful to track this
> further? Are there tools or patches for tracing what the kernel
> gets told by the touchpad, so we could see the nature of these
> parity errors?
Booting with i8042.debug=1 or doing
"echo 1 > /sys/module/i8042/parameters/debug" will dump all data from
the keyboard controller to dmesg. It is quite a bit though (80 pps @ 6
bytes/packet).
--
Dmitry
next prev parent reply other threads:[~2011-11-02 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111030195253.3248.82914.reportbug@debian>
[not found] ` <20111030203044.GB18681@elie.hsd1.il.comcast.net>
[not found] ` <CAAyXcGAC5W5md17=V5rx-kaL7PTmBig4a-4ZhRvAVLVZ7wWzSg@mail.gmail.com>
[not found] ` <20111031092748.GB24978@elie.hsd1.il.comcast.net>
[not found] ` <CAAyXcGCz0Z8xkEin5DVhTa8p6Jc8oOtgghH2EWoSaLrRqCzWdg@mail.gmail.com>
[not found] ` <CAAyXcGDOsmp+PVhHZx3JFjApF2_UbE8dr8jnHKJNDEm5=bWrzA@mail.gmail.com>
2011-11-01 8:02 ` psmouse: "bad data from KBD - bad parity" every 2ms with synaptics touchpad Jonathan Nieder
[not found] ` <CAJm2B-kA63Tifyifd0mRwhaVcr-vdrvk+UGnFHnKwX4=77WL+A@mail.gmail.com>
2011-11-01 19:34 ` Jonathan Nieder
2011-11-02 6:00 ` Dmitry Torokhov [this message]
2011-11-02 6:46 ` Henrik Rydberg
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=20111102060012.GB29035@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=arvindkhadri@gmail.com \
--cc=damjan.jov@gmail.com \
--cc=jrnieder@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
/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