All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-input@vger.kernel.org
Subject: [bisected regression] Touchpad "paste" stops working after suspend to RAM
Date: Sun, 11 Oct 2009 18:21:55 +0200	[thread overview]
Message-ID: <20091011162155.GA4260@Pilar.aei.mpg.de> (raw)

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.

I have a recent dmesg from my laptop here: 

http://www.aei.mpg.de/~crmafra/dmesg-2.6.32-rc3-wifi.txt

(the wifi warnings there are related to another issue, and the touchpad
problem happens independently of those warnings).

I can test patches and provide more info if necessary.


PS: Due to some HAL configuration issue I have this line in my .bashrc

synclient RTCornerButton=2

which makes the right corner region capable of pasting. When the
kernel is "good", it comes back from resume and I don't need to
run this command again for the 'paste' operation to work. When
the kernel is "bad" running this command has no effect and 
"paste" does not work in any way.






             reply	other threads:[~2009-10-11 16:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 16:21 Carlos R. Mafra [this message]
2009-10-11 18:01 ` [bisected regression] Touchpad "paste" stops working after suspend to RAM Dmitry Torokhov
2009-10-11 19:31   ` Carlos R. Mafra
2009-10-12  9:02     ` Dmitry Torokhov
2009-10-12  9:35       ` Carlos R. Mafra
2009-10-12  9:51         ` Carlos R. Mafra
2009-10-12 10:09       ` Carlos R. Mafra
2009-10-13  3:24         ` Dmitry Torokhov
2009-10-13 12:07           ` Carlos R. Mafra
     [not found]           ` <20091013121109.GB4619@Pilar.aei.mpg.de>
     [not found]             ` <20091013182643.GC21593@core.coreip.homeip.net>
     [not found]               ` <20091013190819.GA7555@Pilar.aei.mpg.de>
     [not found]                 ` <20091013194654.GD21593@core.coreip.homeip.net>
     [not found]                   ` <20091013202459.GE21593@core.coreip.homeip.net>
2009-10-13 23:16                     ` Carlos R. Mafra
2009-10-13 23:56                       ` Dmitry Torokhov
2009-10-13 23:57                         ` Dmitry Torokhov
2009-10-14  0:51                           ` Carlos R. Mafra
2009-10-14  2:30                             ` Dmitry Torokhov
2009-10-14 11:13                               ` Carlos R. Mafra
2009-10-15  0:44                                 ` Dmitry Torokhov
2009-10-15 11:08                                   ` Carlos R. Mafra

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=20091011162155.GA4260@Pilar.aei.mpg.de \
    --to=crmafra2@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.