linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Valentin Manea <linux-pm@mrs.ro>
Cc: 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:37:50 +0800	[thread overview]
Message-ID: <1515400670.2578.18.camel@intel.com> (raw)
In-Reply-To: <f9aed3f0e77fc7d3f663fb913e1bb5aa@mrs.ro>

On Mon, 2018-01-08 at 08:21 +0000, Valentin Manea wrote:
> On 2018-01-08 08:13, Zhang Rui wrote:
> > 
> > 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?
> Sure, sorry for not being more specific. I tried both the DE(KDE) 
> suspend functionality but also:
> echo memory  > /sys/power/state
> and the behaviour is the same: display goes dark, system is not 
> responding - the power button which previously wakes up the system 
> doesn't work anymore. It needs a hard reset from this point
> 
> The home button has a slight vibration when device is fully running,
> in 
> this state the vibration doesn't happen at all so I suppose it went 
> through some sleep stages.
> 
> For reference I tried with iommu=off booting because of another bug
> that 
> made the rounds but that never helped. The problem seems to be in the
> 3 
> patches I mentioned in my top email
> 
> > 
> > 
> > 
> > BTW, does the problem still exists in the latest upstream kernel?
> Yep, no changes. System still needs a hard reset after suspending to 
> idle.

in latest upstream kernel, does it work if you use rtcwake instead?
say, "rtcwake -m freeze -s 20"

thanks,
rui
> > 
> > 
> > thanks,
> > rui
> Thanks,
> Valentin
> 

  reply	other threads:[~2018-01-08  8:37 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
2018-01-08  8:21     ` Valentin Manea
2018-01-08  8:37       ` Zhang Rui [this message]
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=1515400670.2578.18.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-pm@mrs.ro \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    /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).