All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Valentin Manea <valy@mrs.ro>,
	linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [BUG] s2idle: Surface Pro 3 suspend/resume issues
Date: Mon, 08 Jan 2018 16:13:44 +0800	[thread overview]
Message-ID: <1515399224.2578.17.camel@intel.com> (raw)
In-Reply-To: <d1c1bab6e2b343abf9105a892dc06c49@mrs.ro>

On Mon, 2018-01-08 at 07:55 +0000, Valentin Manea wrote:
> Again with correct linux-pm
> 
> Hi,
> 
>    Somewhere between 4.12 and 4.13 the s2idle doesn't work anymore on
> the
> Surface Pro 3.

will you please be more specific about the symptom?
what command do you use to do s2idle, and how do you wake it up?


BTW, does the problem still exists in the latest upstream kernel?

thanks,
rui
>    After some bisecting I found 3 patches that seem to be at fault
> ACPI / sleep: EC-based wakeup from suspend-to-idle on recent systems
> ->
> 0f1a83833a0ba93d6986d9e30c8fe35d7d45c17c
> 
> ACPI / PM: Ignore spurious SCI wakeups from suspend-to-idle ->
> 33e4f80ee69b5168badf37edbfed796eb48434b9
> 
> ACPI / PM: Clean up device wakeup enable/disable code ->
> 235d81a630ca2d39818da96f0c14bc960ffbaeb5
> 
>    It doesn't seem to be just one patch, I've tried combinations of
> the
> 3, but only with all three reverted s2idle suspend and resume starts
> working again.
>    I'm not versed in x86 and ACPI so my testing is very coarse
> because
> there is some re-factoring included there. Do you have any idea which
> parts could be casing the problem? Or at least how to debug further?
> 
> Thanks,
> Valentin

  reply	other threads:[~2018-01-08  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85be1584-5260-e7e1-2eda-23607f5a93c2@mrs.ro>
2018-01-08  7:55 ` [BUG] s2idle: Surface Pro 3 suspend/resume issues Valentin Manea
2018-01-08  8:13   ` Zhang Rui [this message]
2018-01-08  8:21     ` Valentin Manea
2018-01-08  8:37       ` Zhang Rui
2018-01-08  9:37         ` Valentin Manea
2018-01-08 11:03       ` Rafael J. Wysocki
2018-01-10 17:03         ` Nick Singer
2018-01-10 22:30           ` Rafael J. Wysocki

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=1515399224.2578.17.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=valy@mrs.ro \
    /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.