From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mikko Vinni <mmvinni@yahoo.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: keyboard leds not restored after s2ram in 2.6.32-rc6-00166-g799dd75
Date: Wed, 11 Nov 2009 14:14:14 -0800 [thread overview]
Message-ID: <20091111215029.GA13390@core.coreip.homeip.net> (raw)
In-Reply-To: <800885.42568.qm@web58401.mail.re3.yahoo.com>
On Wed, Nov 11, 2009 at 12:05:42PM -0800, Mikko Vinni wrote:
> Hi,
>
> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> > > my laptop shows the caps lock and scroll lock leds as being on after s2ram
> > > (and resume), even though they are off. If I press the caps lock key, the caps
> > > lock led stays on, the num lock led turns off, and the screen unlock screen
> > > warns about the caps lock being on.
> > >
> >
> > Thank you for the report. Could youplease tell me if the patch below
> > fixes the problem?
>
> Yes, it does. Thanks, now my HP-dv5 is happy.
>
> I did some tests suspending with the caps lock actually on, and it seems that
> in that case the user might still be confused (caps lock is on but led is off).
> At least on this machine this patch doesn't affect this theoretical problem
> either way (2.6.31 behaves similarly), so it is ok.
>
Umm... so you are saying that even with .31 if you suspend with capslock
on it is off when you resume? Does it happen only in X or in console as
well?
--
Dmitry
next prev parent reply other threads:[~2009-11-11 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:27 keyboard leds not restored after s2ram in 2.6.32-rc6-00166-g799dd75 Mikko Vinni
2009-11-11 9:52 ` Dmitry Torokhov
2009-11-11 20:05 ` Mikko Vinni
2009-11-11 22:14 ` Dmitry Torokhov [this message]
2009-11-12 8:08 ` Mikko Vinni
2009-11-26 2:14 ` Dmitry Torokhov
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=20091111215029.GA13390@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmvinni@yahoo.com \
/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).