public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Pavel Machek <pavel@ucw.cz>,
	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:00:09 +0200	[thread overview]
Message-ID: <1459260009.5124.5.camel@suse.com> (raw)
In-Reply-To: <4224351.Xlkh4fNNHG@vostro.rjw.lan>

On Tue, 2016-03-29 at 15:06 +0200, 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.

Not necessarily. ACPI may also be the root cause.

> 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.

What does /proc/acpi/wakeup say?

	Regards
		Oliver

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

Thread overview: 9+ 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 [this message]
2016-03-29 14:15     ` Pavel Machek
2016-03-29 14:24   ` Pavel Machek
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

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=1459260009.5124.5.camel@suse.com \
    --to=oneukum@suse.com \
    --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=pavel@ucw.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox