From: "Kenneth R. Crudup" <kenny@panix.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
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 fix a regression caused by 56b9918490 (PM: sleep: Simplify suspend-to-idle control flow)
Date: Mon, 25 Nov 2019 12:19:23 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.1911251213200.2817@hp-x360n> (raw)
In-Reply-To: <alpine.DEB.2.21.1911251155440.2817@hp-x360n>
On Mon, 25 Nov 2019, Kenneth R. Crudup wrote:
> Had to do a long- power-button reset to get it back up again.
Datapoint that may be useful- when I have to do the hard power cycle after
a failed suspend, the ports on this laptop (2x USB-C/Thunderbolt 3) get
totally wedged up- the charging light stays on even if there's nothing
plugged into either port, and USB/TB operation is almost always wedged
up (devices not recognized). I have to use a special key sequence (hold
down F6 and power at the same time for several seconds) to get it unwedged.
The system seems to also think the laptop is charging as well, even with
nothing plugged into either port. It's like something in the ACPI/BIOS
doesn't get "unsuspended" either.
I used to have TB and USB as modules that would get unloaded at suspend to
see if those were related to this issue, but that only seemed to make idle
power draw even higher for some reason.
-Kenny
--
Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley
next prev parent reply other threads:[~2019-11-25 20:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 0:11 Help me fix a regression caused by 56b9918490 (PM: sleep: Simplify suspend-to-idle control flow) Kenneth R. Crudup
2019-11-22 10:12 ` Rafael J. Wysocki
2019-11-22 12:45 ` Rafael J. Wysocki
2019-11-22 17:35 ` Kenneth R. Crudup
2019-11-23 10:24 ` Kenneth R. Crudup
2019-11-24 16:02 ` Rafael J. Wysocki
2019-11-25 3:40 ` Kenneth R. Crudup
2019-11-25 13:27 ` Rafael J. Wysocki
2019-11-25 14:14 ` Rafael J. Wysocki
2019-11-25 18:27 ` Kenneth R. Crudup
2019-11-25 20:11 ` Kenneth R. Crudup
2019-11-25 20:19 ` Kenneth R. Crudup [this message]
2019-11-25 22:01 ` Rafael J. Wysocki
2019-11-25 23:32 ` Kenneth R. Crudup
2019-11-26 8:50 ` Rafael J. Wysocki
2019-11-26 16:12 ` Rafael J. Wysocki
2019-11-26 16:15 ` Kenneth R. Crudup
2019-11-26 16:27 ` Rafael J. Wysocki
2019-11-26 16:35 ` Kenneth R. Crudup
2019-11-26 18:48 ` Rafael J. Wysocki
2019-11-26 19:03 ` Kenneth R. Crudup
2019-11-26 19:09 ` Rafael J. Wysocki
2019-11-26 19:13 ` Kenneth R. Crudup
2019-11-26 19:45 ` Kenneth R. Crudup
2019-11-26 23:56 ` Kenneth R. Crudup
2019-11-27 2:35 ` Kenneth R. Crudup
2019-11-27 8:31 ` Rafael J. Wysocki
2019-11-27 22:30 ` Kenneth R. Crudup
2019-11-28 16:25 ` Rafael J. Wysocki
2019-11-25 21:47 ` Rafael J. Wysocki
2019-11-25 16:21 ` Kenneth R. Crudup
2019-11-25 21:46 ` Rafael J. Wysocki
2019-11-25 23:02 ` Kenneth R. Crudup
2019-11-26 8:53 ` Rafael J. Wysocki
2019-11-25 5:50 ` Kenneth R. Crudup
2019-11-25 7:17 ` Kenneth R. Crudup
2019-11-22 17:29 ` 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.1911251213200.2817@hp-x360n \
--to=kenny@panix.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).