From: Ye Shu <hello@shuye.dev>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Dima Ruinskiy <dima.ruinskiy@intel.com>,
Vitaly Lifshits <vitaly.lifshits@intel.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000e: add Dell Pro 5 Micro P5M1260 to disable K1 list
Date: Thu, 19 Nov 2026 17:54:50 -0800 [thread overview]
Message-ID: <c4801ff7-7ff6-457e-b0a5-c2e633d35c59@shuye.dev> (raw)
In-Reply-To: <20261119001818.513503-1-acelan.kao@canonical.com>
Hi Chia-Lin and others,
On 11/18/26 4:18 PM, Chia-Lin Kao (AceLan) wrote:
> K1 was re-enabled on MTL and later platforms by
> commit 578294b8b60d ("e1000e: Reconfigure PLL clock gate timeout and re-enable K1 on Meteor Lake").
> Since then, the Dell Pro 5 Micro P5M1260 (Panther Lake, I219
> [8086:57b3]) no longer enters S0ix during s2idle.
I have independently reproduced a similar S0ix issue on a different
machine, an HP ZBook 8 G2i 14 (also Panther Lake, with Intel I219 NIC
[8086:57b3] using the e1000e driver).
Machine tested:
- Model: HP ZBook 8 G2i 14
- DMI system vendor: HP
- DMI product name: HP ZBook 8 G2i 14 inch Mobile Workstation PC
- DMI base board product name: 8ED9
- NIC: Intel I219-LM [8086:57b3], subsystem Hewlett-Packard Company
Device [103c:8ed9], driver e1000e
- Distribution: Fedora 45
- Kernel: 7.3.4-300.fc45.x86_64
- BIOS: Y70 Ver. 01.01.07
With K1 enabled by default (disable-k1: off), S0ix entry is
intermittent. Some suspend go into S0ix while others do not, even with
CPU reaching Package C10.
> Every suspend ends with:
>
> intel_pmc_core INT33A1:00: CPU did not enter SLP_S0!!! (S0ix cnt=0)
Failed suspend produces the same message:
intel_pmc_core INT33A1:00: CPU did not enter SLP_S0!!!
> The PMC low power mode status dump shows the GbE IP is never power
> gated (GBE_PGD0_PG_STS, GBE_D3_STS and GBE_VNN_REQ_STS all 0), while
> the CPU itself reaches C10.
The PMC dump shows the following:
CPU_C10_REQ_STS 1
GBE_PGD0_PG_STS 0
GBE_D3_STS 1
GBE_VNN_REQ_STS 0
> Disabling K1 at runtime restores S0ix on the same unit, kernel and
> BIOS:
>
> # ethtool --set-priv-flags enp0s31f6 disable-k1 on
Disabling K1 using the same command appears to resolve the problem. I
performed the following A/B/A test within a single boot, using 120
second rtcwake -m mem cycles and measuring slp_s0_residency_usec before
and after each cycle:
disable-k1 on: 6/6 successful (~116-119 s in S0ix)
disable-k1 off: 1/4 successful (118, 0, 0, 0 s in S0ix)
disable-k1 on: 4/4 successful (~115-119 s in S0ix)
Since this issue also reproduces on a different machine with the same
PCI device ID for NIC, would you prefer adding another HP-specific DMI
entry to disable_k1_list, or do you think that disabling K1 for all NICs
with PCI ID [8086:57b3] would be more appropriate?
I'm happy to submit a separate disable_k1_list patch or test any
proposed changes.
Thank you!
Ye
parent reply other threads:[~2026-11-20 1:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20261119001818.513503-1-acelan.kao@canonical.com>]
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=c4801ff7-7ff6-457e-b0a5-c2e633d35c59@shuye.dev \
--to=hello@shuye.dev \
--cc=acelan.kao@canonical.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=vitaly.lifshits@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
all inboxes | Powered by JetHome®