From: "Rafael J. Wysocki" <rafael@kernel.org>
To: "Kenneth R. Crudup" <kenny@panix.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
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 16:38:26 +0200 [thread overview]
Message-ID: <CAJZ5v0hvauVP1NsQq8FTTf0_hk4_KujmCJTAE8ry43gu7wQ-GQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1909190444190.2973@hp-x360n>
On Thu, Sep 19, 2019 at 1:46 PM Kenneth R. Crudup <kenny@panix.com> wrote:
>
>
> On Thu, 19 Sep 2019, Rafael J. Wysocki wrote:
>
> > You may still be able to use S3 on this machine if that's supported by
> > the platform firmware.
>
> It's not; I tried "deep" two days after getting it.
>
> > I would recommend to try 5.4-rc1 when it's out to see if the problems
> > above are still there.
>
> Well, I'm running Linus' master tip right now and pull and run the latest
> bleeding-edge kernel daily;
Specifically, the material I had in mind was merged on Tuesday, so I
guess you're running it by now.
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).
> does this mean you have further patches coming
> down the line later?
There may be a couple, but not related to the EC.
next prev parent reply other threads:[~2019-09-19 14:38 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 [this message]
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
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=CAJZ5v0hvauVP1NsQq8FTTf0_hk4_KujmCJTAE8ry43gu7wQ-GQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=kenny@panix.com \
--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).