kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: jingyun@cpu-os.ac.cn (jingyun at cpu-os.ac.cn)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB keyboard can NOT wakeup from S3( suspend to RAM )
Date: Thu, 31 Aug 2017 06:38:48 +0800	[thread overview]
Message-ID: <201708310638479525595@cpu-os.ac.cn> (raw)
In-Reply-To: 20170830060955.GE3035@kroah.com

Hi, Greg

Thanks for your time.
First of all, if I do NOT hit the keyboard during the suspend.
Then my keyboard CAN wake the system up from suspend.
This has rule out that my system does NOT support USB wakeup. Right ?

Thanks again.

Jim


 
From: Greg KH
Date: 2017-08-30 14:09
To: jingyun at cpu-os.ac.cn
CC: kernelnewbies
Subject: Re: USB keyboard can NOT wakeup from S3( suspend to RAM )
On Wed, Aug 16, 2017 at 06:03:22PM +0800, 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.
> 
> 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.
 
Sounds like your system does not support USB wakeup, which is very
common, sorry.
 
good luck!
 
greg k-h
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170831/190228e3/attachment.html 

  parent reply	other threads:[~2017-08-30 22:38 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 [this message]
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
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=201708310638479525595@cpu-os.ac.cn \
    --to=jingyun@cpu-os.ac.cn \
    --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).