From: "Kenneth R. Crudup" <kenny@panix.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rafael Wysocki <rafael.j.wysocki@intel.com>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: Help me help you debug what seems to be an EC resume issue
Date: Thu, 19 Sep 2019 10:10:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1909191004300.2842@hp-x360n> (raw)
In-Reply-To: <CAJZ5v0iQp4MNCY-ksGTaTntnmaARSZaOW4sX49zqavtSUvo=Xw@mail.gmail.com>
On Thu, 19 Sep 2019, Rafael J. Wysocki wrote:
> I would recommend to read
> https://01.org/blogs/qwang59/2018/how-achieve-s0ix-states-linux
> at this point if you have not done it yet.
Yeah, I have ... and I get this after a resume:
> intel_pmc_core INT33A1:00: CPU did not enter SLP_S0!!! (S0ix cnt=0)
... and this even after multiple suspend/resume cycles:
> /sys/kernel/debug/pmc_core/slp_s0_residency_usec:0
I did determine I'm going in to C10 though, but that's a "when powered on"
issue; I'm trying to maximize the time I get in s2idle- it's the only thing
infuriating about this laptop. Hibernate works, and I do that when I know
I won't be using it for a while, but going from a laptop that would give me
nearly a week in S3 to this one where I can lose ~20-35% overnight sucks and
I've been pulling at any straw trying to reduce s2idle power draw.
-Kenny
--
Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley
next prev parent reply other threads:[~2019-09-19 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 1:05 Help me help you debug what seems to be an EC resume issue Kenneth R. Crudup
2019-09-19 7:39 ` Rafael J. Wysocki
2019-09-19 11:46 ` Kenneth R. Crudup
2019-09-19 14:38 ` Rafael J. Wysocki
2019-09-19 16:09 ` Kenneth R. Crudup
2019-09-19 16:13 ` Kenneth R. Crudup
2019-09-19 16:35 ` Kenneth R. Crudup
2019-09-19 16:52 ` Kenneth R. Crudup
2019-09-19 16:53 ` Rafael J. Wysocki
2019-09-19 17:10 ` Kenneth R. Crudup [this message]
2019-09-19 17:13 ` Kenneth R. Crudup
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=alpine.DEB.2.21.1909191004300.2842@hp-x360n \
--to=kenny@panix.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.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).