linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bruno Pr??mont <bonbons@linux-vserver.org>
Cc: Linux Input <linux-input@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"R. J. Wysocki" <Rafal.Wysocki@fuw.edu.pl>
Subject: Re: Input+S3: extra keycodes forgotten after suspend
Date: Wed, 21 May 2008 16:38:08 -0400	[thread overview]
Message-ID: <20080521163638.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080521220833.2e4345cb@neptune.home>

On Wed, May 21, 2008 at 10:08:33PM +0200, Bruno Pr??mont wrote:
> Hi Dmitry,
> 
> On Wed, 21 May 2008 Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > Hi Bruno,
> > 
> > On Mon, May 19, 2008 at 06:45:01PM +0200, Bruno Pr??mont wrote:
> > > Hi Dmitry,
> > > 
> > > Please find attached dmesg output.
> > > 
> > > The suspend process looked somewhat like the following:
> > > - quick test of 
> > >     echo 1 > /sys/modules/i8042/parameters/debug
> > >   and disabled it again
> > >     echo 0 > /sys/modules/i8042/parameters/debug
> > > - exit X and rmmod usb-storage and a few other modules
> > >   (nfs, xfs and the like).
> > > - checked the extra keys (showkey) and enabled debug again
> > > - echo mem > /sys/power/state
> > > 
> > > Wait half a minute with laptop in S3
> > > 
> > > - hit enter to resume
> > > - wait a bit, as it takes too long help out with short
> > >   presses on power button (somehow it helps the HDD/CDROM
> > >   to resume), also pressed caps-lock when graphics were
> > >   resumed and cursor blinking (very slowly)
> > > - once userspace was awake again check extra keys with
> > >   showkeys
> > > - disabled input debug
> > > 
> > > I hope this is detailed enough.
> > > 
> > > List of patches applied to linux-2.6.25.4:
> > >   http://lkml.org/lkml/2008/5/16/430
> > >   http://lkml.org/lkml/2008/5/16/429
> > >   squashfs
> > > 
> > 
> > Question - does the problem happen if you dont have dritek extension
> > enabled (i.e. on unpatched kernel)?
> 
> When running 2.6.25.4 without the two dritek patches it does not
> redetect the keyboard (but obviously the extra keys don't work at all)
> 

Ah, ok, great.. I think we simply need to move dritek out of the place
where you put it in so it does not interfere with our efforts to
resume keyboard and mouse ;) I will see what I can do there..

-- 
Dmitry

  reply	other threads:[~2008-05-21 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 20:25 Input+S3: extra keycodes forgotten after suspend Bruno Prémont
2008-05-16 20:38 ` Dmitry Torokhov
2008-05-16 21:00   ` Bruno Prémont
2008-05-19 15:50     ` Dmitry Torokhov
2008-05-19 16:45       ` Bruno Prémont
2008-05-21 17:55         ` Dmitry Torokhov
2008-05-21 20:08           ` Bruno Prémont
2008-05-21 20:38             ` Dmitry Torokhov [this message]
2008-05-23  4:44               ` Dmitry Torokhov
2008-05-23 20:57                 ` Bruno Prémont
2008-05-27  5:52                   ` Dmitry Torokhov
2008-05-27 20:52                     ` Bruno Prémont

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=20080521163638.ZZRA012@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=Rafal.Wysocki@fuw.edu.pl \
    --cc=bonbons@linux-vserver.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).