Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751975AbZJKTc6 (ORCPT ); Sun, 11 Oct 2009 15:32:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751195AbZJKTc5 (ORCPT ); Sun, 11 Oct 2009 15:32:57 -0400 Received: from ox1.aei.mpg.de ([194.94.224.6]:59623 "EHLO ox1.aei.mpg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbZJKTc4 (ORCPT ); Sun, 11 Oct 2009 15:32:56 -0400 Date: Sun, 11 Oct 2009 21:31:00 +0200 From: "Carlos R. Mafra" To: Dmitry Torokhov Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , linux-input@vger.kernel.org Subject: Re: [bisected regression] Touchpad "paste" stops working after suspend to RAM Message-ID: <20091011193100.GA4410@Pilar.aei.mpg.de> References: <20091011162155.GA4260@Pilar.aei.mpg.de> <20091011180134.GA5197@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091011180134.GA5197@core.coreip.homeip.net> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1444 Lines: 33 On Sun 11.Oct'09 at 11:01:34 -0700, Dmitry Torokhov wrote: > Hi Carols, > > On Sun, Oct 11, 2009 at 06:21:55PM +0200, Carlos R. Mafra wrote: > > Using the latest 2.6.32-rc3+ kernel, the "paste" operation via the > > touchpad of my Vaio laptop does not work after suspend to RAM. > > > > It works flawlessly before s2ram; I select the text with the touchpad > > and tap quickly its right corner to paste the selected text. > > After a plain 'echo mem > /sys/power/state' the "paste" does not work. > > > > I bisected it to commit ffd0db97196c1057f09c2ab42dd5b30e94e511d9 ("Input: > > add generic suspend and resume for input devices"). > > > > I haven't tested if reverting it from mainline fixes the issue, but > > from the patch description I guess that bisection landed correctly > > on the culprit. > > > > Please verify that this is the real offending commit by reverting it - I > am surprised that it would give any trouble since it is supposed to > restore LED state and repeat rate and therefore should only be affecting > keyboards. Reverting it fixes the issue, I've just tested it now. [ I had to edit the resulting drivers/input/input.c because it did not revert cleanly. ] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/