From: martink@posteo.de (Martin Kepplinger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB keyboard can NOT wakeup from S3( suspend to RAM )
Date: Tue, 05 Sep 2017 08:32:37 +0200 [thread overview]
Message-ID: <15b51dc216a61f8169ef26bc29a2b4ae@posteo.de> (raw)
In-Reply-To: <2017083107065750873319@cpu-os.ac.cn>
Am 31.08.2017 01:06 schrieb jingyun at cpu-os.ac.cn:
> Hi, Andrey
>
> Q:
> Do you mean that wakeup by keyboard doesn't work only if PC was
> suspended by pressing special suspend key on your keyboard?
>
> Answer?
> No.
> Wakeup by keyboard doesn't work only if I pressing the keyboard (fast
> enough) during the suspend.
> It has nothing to do with suspending method.
>
> Q:
> And if it was suspended by from operating system or by pressing button
> on case wakeup by keyboard does work?
>
> Answer:
> The problem has nothing to do with suspending method.
> Whatever the suspending method is( from desktop or echo mem >
> /sys/power/stat ), if I do NOT hit the keyboard during the suspend,
> then
> wakeup by keyboard does work.
> But if I hit the keyboard fast enough during the suspend, then after
> the suspend the keyboard seems dead.
> And wakeup by keyboard does NOT work any more.
>
> Thanks for your time.
>
> Jim
>
> -------------------------
>
>> FROM: Andrey Skvortsov
>> DATE: 2017-08-30 15:45
>> TO: jingyun at cpu-os.ac.cn
>> CC: kernelnewbies
>> SUBJECT: Re: USB keyboard can NOT wakeup from S3( suspend to RAM )
>>
>> On 17-08-16 18:03, jingyun at cpu-os.ac.cn wrote:
>>> hi, there
>>>
>>> thx in advance;
>>>
>>> I encounter a strange (maybe) bug:
>>> During the suspending of my linux box(which runs debian 9), I hit
>> the key of the USB interfaced keyboard;
>>> after making sure the box enter suspend state for a while ( which
>> I can tell from the power LED blinks),
>>> I can NOT wakeup it by hit that keyboard any more.
>>> But if I do NOT hit the key during the suspending, I CAN wake it
>> up by hitting the keyboard.
>>
>> Do you mean that wakeup by keyboard doesn't work only if PC was
>> suspended by pressing special suspend key on your keyboard?
>> And if it was suspended by from operating system or by pressing
>> button
>> on case wakeup by keyboard does work?
>>
>>> After that I tried Ubuntu 16.04(runs 4.4 version kernel ) and
>> Ubuntu 14.04 ( 3.13 kernel).
>>> And I found all of them got the same problem;
>>>
>>> Do not know if this is the right place to ask. Just a try.
>>>
>>> Thanks again.
Sounds like a bug. Doesn't *have* to be in the kernel though. At least
it sounds like
pressing buttons "during" suspending resets a state to resumed before it
actually
suspended - preventing to resume...
Is it an ordanary usb keyboard? Could you append the output of lsmod,
the modules
you are using and lsusb?
next prev parent reply other threads:[~2017-09-05 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 10:03 USB keyboard can NOT wakeup from S3( suspend to RAM ) jingyun at cpu-os.ac.cn
2017-08-30 6:09 ` Greg KH
2017-08-30 6:55 ` valdis.kletnieks at vt.edu
2017-08-30 22:38 ` jingyun at cpu-os.ac.cn
2017-08-31 7:16 ` Greg KH
2017-09-05 1:51 ` jingyun at cpu-os.ac.cn
2017-08-30 7:45 ` Andrey Skvortsov
2017-08-30 23:06 ` jingyun at cpu-os.ac.cn
2017-09-05 6:32 ` Martin Kepplinger [this message]
2017-09-05 2:20 ` jingyun at cpu-os.ac.cn
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=15b51dc216a61f8169ef26bc29a2b4ae@posteo.de \
--to=martink@posteo.de \
--cc=kernelnewbies@lists.kernelnewbies.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).