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:52:41 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1909190951590.2842@hp-x360n> (raw)
In-Reply-To: <alpine.DEB.2.21.1909190930190.2842@hp-x360n>
This is after a resume. Maybe this is helpful, too?
----
[ +0.002487] intel_pmc_core INT33A1:00: CPU did not enter SLP_S0!!! (S0ix cnt=0)
[ +0.000005] intel_pmc_core INT33A1:00: SLP_S0_DBG: AUDIO_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: OTG_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: XHCI_D3 State: Yes
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: LPIO_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: SDX_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: SATA_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: UFS0_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: UFS1_D3 State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: EMMC_D3 State: Yes
[ +0.000005] intel_pmc_core INT33A1:00: SLP_S0_DBG: SDIO_PLL_OFF State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: USB2_PLL_OFF State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: AUDIO_PLL_OFF State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: OC_PLL_OFF State: Yes
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: MAIN_PLL_OFF State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: XOSC_OFF State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: LPC_CLKS_GATED State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: PCIE_CLKREQS_IDLE State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: AUDIO_ROSC_OFF State: Yes
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: HPET_XOSC_CLK_REQ State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: PMC_ROSC_SLOW_CLK State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: AON2_ROSC_GATED State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: CLKACKS_DEASSERTED State: No
[ +0.000004] intel_pmc_core INT33A1:00: SLP_S0_DBG: MPHY_CORE_GATED State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: CSME_GATED State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: USB2_SUS_GATED State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: DYN_FLEX_IO_IDLE State: Yes
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: GBE_NO_LINK State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: THERM_SEN_DISABLED State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: PCIE_LOW_POWER State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: ISH_VNNAON_REQ_ACT State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: ISH_VNN_REQ_ACT State: No
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: CNV_VNNAON_REQ_ACT State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: CNV_VNN_REQ_ACT State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: NPK_VNNON_REQ_ACT State: No
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: PMSYNC_STATE_IDLE State: Yes
[ +0.000001] intel_pmc_core INT33A1:00: SLP_S0_DBG: ALST_GT_THRES State: Yes
[ +0.000002] intel_pmc_core INT33A1:00: SLP_S0_DBG: PMC_ARC_PG_READY State: No
----
-Kenny
--
Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley
next prev parent reply other threads:[~2019-09-19 16:52 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 [this message]
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.1909190951590.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).