All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:09:39 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1909190857260.2973@hp-x360n> (raw)
In-Reply-To: <CAJZ5v0hvauVP1NsQq8FTTf0_hk4_KujmCJTAE8ry43gu7wQ-GQ@mail.gmail.com>


On Thu, 19 Sep 2019, Rafael J. Wysocki wrote:

> If so, you can try writing 1 into
> /sys/module/acpi/parameters/sleep_no_lps0 and see if that makes any
> difference (without using ec_no_wakeup).

I'll try that soon; in a classic case of "it never makes that sound at the
mechanic's shop" I've done some 6+ sleep cycles since E-mailing you (and
with "ec_no_wakeup" off), and all have come back OK. Increased power drain
during random suspend cycles is still an issue, though, but that may be
unrelated.

(I did remove the MEI driver from the kernel, as I was seeing error returns
during probing on the resume end with "no_console_suspend/initcall_debug" on,
but I'd be surprised if that were an issue here.  I have no need for the MEI
at all, but it's been my experience that loading drivers for devices seem to
reduce the power consumption in s2idle even if I don't (directly) use them
(i.e., I see higher s2idle power drain if I don't enable the "skl_uncore" driver).)

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Silicon Valley

  reply	other threads:[~2019-09-19 16:09 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 [this message]
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
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.1909190857260.2973@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 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.