From: Alexander Lam <lambchop468@gmail.com>
To: linux-input@vger.kernel.org
Subject: Bug: Short reset of ps/2 mouse causes Synaptics touchpad misdetection
Date: Sun, 4 Apr 2010 11:58:06 -0400 [thread overview]
Message-ID: <s2ydfb03c971004040858p6872d1f4p3fc0f8dac1fbd2e6@mail.gmail.com> (raw)
Hi,
Please CC: me when replying
I have filed a bug on the kernel bug tracker, #15636,
https://bugzilla.kernel.org/show_bug.cgi?id=15636.
Description:
The commit
commit 4a299bf591bc5bef3bde8316e603b9eaec5a7696
author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
date: Fri, 25 Dec 2009 05:40:24 +0000 (21:40 -0800)
Input: speed up suspend/shutdown for PS/2 mice and keyboards
Instead of doing full-blown reset while suspending or shutting down
the box use lighter form of reset that should take less time.
(I didn't do a full bisection, but I reversed this just this commit on a hunch,
and it made my problems go away)
Causes ~50% misdetection rate of the Synaptics touchpad upon reboot on an Acer
Aspire One AOA150.
Sometimes, the touchpad is detected as a plain mouse, and sometimes it is
detected as a Synaptics device.
Relevant dmesg sections:
Good Boot:
Mar 6 12:29:30 lamtop kernel: [ 3.201052] Synaptics Touchpad, model: 1, fw:
7.2, id: 0x1c0b1, caps: 0xd04771/0xa40000
Mar 6 12:29:30 lamtop kernel: [ 3.263016] input: SynPS/2 Synaptics TouchPad
as /devices/platform/i8042/serio2/input/input6
Bad Boot:
Feb 12 08:16:12 lamtop kernel: [ 4.060365] input: PS/2 Generic Mouse as
/devices/platform/i8042/serio2/input/input6
I am posting this to the list because there hasn't been any movement on this
bug since last week when it was filed. It also appears that the server
hosting the mailing list that the kernel input bugs are assigned to is down
(no ping, no nmap results to email ports)
--
Alexander Lam
next reply other threads:[~2010-04-04 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 15:58 Alexander Lam [this message]
2010-04-04 17:35 ` Bug: Short reset of ps/2 mouse causes Synaptics touchpad misdetection Christoph Fritz
2010-04-10 20:00 ` Alexander Lam
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=s2ydfb03c971004040858p6872d1f4p3fc0f8dac1fbd2e6@mail.gmail.com \
--to=lambchop468@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).