[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2009 14:14:14 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Mikko Vinni <mmvinni@...oo.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: keyboard leds not restored after s2ram in
2.6.32-rc6-00166-g799dd75
On Wed, Nov 11, 2009 at 12:05:42PM -0800, Mikko Vinni wrote:
> Hi,
>
> From: Dmitry Torokhov <dmitry.torokhov@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists