From: Dmitry Torokhov Subject: Re: Bug: touchpad unresponsive after resume from S3 (psmouse driver) Date: Tue, 29 Nov 2011 09:53:33 -0800 Message-ID: <20111129175333.GE4241@core.coreip.homeip.net> References: <4ED507AB.6040905@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:57964 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751530Ab1K2Rxj (ORCPT ); Tue, 29 Nov 2011 12:53:39 -0500 Received: by qyk4 with SMTP id 4so1830628qyk.19 for ; Tue, 29 Nov 2011 09:53:39 -0800 (PST) Content-Disposition: inline In-Reply-To: <4ED507AB.6040905@canonical.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Daniel Manrique Cc: linux-input@vger.kernel.org Hi Daniel, On Tue, Nov 29, 2011 at 11:26:19AM -0500, Daniel Manrique wrote: > Hello, > > I apologize for sending this bug report directly; with the kernel.org bugtracker > down I was told this was the best option for the time being. If this is not > correct, could you please let me know of a good place to submit this bug report? > > I have several Dell laptops with Synaptics touchpads, particularly a group of > Vostro V13 systems. On these, after a suspend/resume cycle, the touchpad > (Synaptics) is unresponsive; a workaround is to rmmod psmouse; modprobe psmouse. > > This was first reported on kernel 2.6.38, although I think the issue has been > present from as early as 2.6.32. I verified it for sure with Ubuntu 2.6.38 > kernels, 3.0.0 kernels, and a 3.2.0 kernel from the development release, as well > as a "mainline" 3.1.0-rc10 kernel. > > Since this problem was seen on Ubuntu, it's filed on the Launchpad bug tracker. > The first report I can find is this one: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/715267 > > This includes a series of log messages I don't see on my systems. I then filed > this other bug: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879650 > > The last one contains specific information from one of my systems (a Vostro V13). > > I'd really appreciate any help or guidance on how to solve this problem. If you > need me to collect any information or run any tests on these machines, please > don't hesitate to ask, these systems are primarily used for testing. > Please do: - enable i8042 debug (echo 1 > /sys/module/i8042/parameters/debug) - rmmod psmouse; - suspend/resume; - collect dmesg; - suspend/resume; - collect dmesg again and we'll have to try and find what we do differently. Thanks. -- Dmitry