All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	lenb@kernel.org, linux-acpi@vger.kernel.org,
	Linux PM list <linux-pm@vger.kernel.org>,
	Jiri Kosina <jikos@kernel.org>
Subject: Re: Changes in sleep mode, on x86 PC
Date: Tue, 29 Mar 2016 16:24:05 +0200	[thread overview]
Message-ID: <20160329142405.GA24781@amd> (raw)
In-Reply-To: <4224351.Xlkh4fNNHG@vostro.rjw.lan>


On Tue 2016-03-29 15:06:36, Rafael J. Wysocki wrote:
> On Monday, March 28, 2016 11:20:12 PM Pavel Machek wrote:
> > Hi!
> > 
> > Few releases ago, I could wake up PC from S3 sleep by hitting any
> > key. That ceased to work some time before, keyboard would just light a
> > NUM lock LED when I hit a key (4.5). Now PC seems to be sleeping (in
> > S3) with NUM lock LED on (4.6-rc0).
> > 
> > Any idea what is going on there? Does it happen for you, too? What is
> > the expected behaviour?
> >
> > Debian 8.3, with MATE desktop, I just hit the "moon" key to make it
> > sleep. Keyboard is on USB.
> 
> That's rather important.
> 
> Clearly, something in the USB HID land has changed lately.
> 
> The expected behavior depends on whether or not the keyboard itself and the
> USB controller are both enabled to wake up.  If they are, I'd expect any
> key press to generate a wakeup event.

Is there anything in /sys I should check?

pavel@amd:/sys/class/input/input43$ ls
capabilities  id			 input43::scrolllock  phys
 subsystem
 device	      input43::capslock  modalias	      power
 uevent
 event8	      input43::numlock	 name		      properties  uniq
 pavel@amd:/sys/class/input/input43$ cat power/
 async                   runtime_active_kids     runtime_status
 autosuspend_delay_ms    runtime_active_time
 runtime_suspended_time
 control                 runtime_enabled         runtime_usage
 pavel@amd:/sys/class/input/input43$ cat power/

Ok, this is slightly weird, but it seems to be just multimedia keys
having separate device:

pavel@amd:/sys/class/input$ grep . input4*/name
input43/name:Chicony USB Keyboard
input44/name:Chicony USB Keyboard

pavel@amd:/sys/class/input$ ls input43/
capabilities  id	        input43::scrolllock  phys
subsystem
device	      input43::capslock  modalias	      power
uevent
event8	      input43::numlock	 name		      properties  uniq
pavel@amd:/sys/class/input$ ls input44
capabilities  event9  modalias phys   properties  uevent
device	            id      name      power  subsystem   uniq


Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2016-03-29 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 21:20 Changes in sleep mode, on x86 PC Pavel Machek
2016-03-29 13:06 ` Rafael J. Wysocki
2016-03-29 14:00   ` Oliver Neukum
2016-03-29 14:15     ` Pavel Machek
2016-03-29 14:24   ` Pavel Machek [this message]
2016-03-29 21:46     ` Rafael J. Wysocki
2016-03-29 21:56       ` Pavel Machek
2016-03-29 22:04         ` Rafael J. Wysocki
2016-03-30 14:48           ` Alan Stern
2016-03-30 14:48             ` Alan Stern

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=20160329142405.GA24781@amd \
    --to=pavel@ucw.cz \
    --cc=jikos@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.