From: Jonathan Nieder <jrnieder@gmail.com>
To: linux-input@vger.kernel.org
Cc: Arvind K <arvindkhadri@gmail.com>, Dmitry Torokhov <dtor@mail.ru>,
Damjan Jovanovic <damjan.jov@gmail.com>
Subject: psmouse: "bad data from KBD - bad parity" every 2ms with synaptics touchpad
Date: Tue, 1 Nov 2011 03:02:11 -0500 [thread overview]
Message-ID: <20111101080210.GB4566@elie.hsd1.il.comcast.net> (raw)
In-Reply-To: <CAAyXcGDOsmp+PVhHZx3JFjApF2_UbE8dr8jnHKJNDEm5=bWrzA@mail.gmail.com>
(cc-ing some people in case they have clues)
Hi Dmitry et al,
Arvind K explains at [1]:
He owns a Synaptics touchpad and has been using it for a while. Every
once in a while it stops responding. Running "modprobe -r psmouse &&
modprobe psmouse" gets it working again.
On investigation, we learn that the message
psmouse.c: bad data from KBC - bad parity
appears in dmesg approximately every 2 milliseconds when this happens.
The touchpad worked without trouble since this system was installed,
in February. The bug only surfaced recently, when he changed the X
configuration somehow.
Userland is Debian 6.0.x (squeeze).
The problem is reproducible with:
- Debian's 2.6.32-38 (which is based on v2.6.32.43)
- 2.6.39-3~bpo60+1 (based on v2.6.39.2)
- 3.1.0~rc7-1~experimental.1 (very close to v3.1-rc7)
Hardware:
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa40000/0xa0000
More details are in the original report at [1]. Any ideas for
tracking this down?
Thanks for keeping the input subsystem in good shape.
Jonathan
[1] http://bugs.debian.org/647136
next parent reply other threads:[~2011-11-01 8:02 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 ` Jonathan Nieder [this message]
[not found] ` <CAJm2B-kA63Tifyifd0mRwhaVcr-vdrvk+UGnFHnKwX4=77WL+A@mail.gmail.com>
2011-11-01 19:34 ` psmouse: "bad data from KBD - bad parity" every 2ms with synaptics touchpad Jonathan Nieder
2011-11-02 6:00 ` Dmitry Torokhov
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=20111101080210.GB4566@elie.hsd1.il.comcast.net \
--to=jrnieder@gmail.com \
--cc=arvindkhadri@gmail.com \
--cc=damjan.jov@gmail.com \
--cc=dtor@mail.ru \
--cc=linux-input@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