Public bug reported:
[Impact]
Dell systems with Intel Panther Lake and onboard Intel I219 ethernet
([8086:57b3], e1000e driver) fail to enter S0ix hardware sleep during s2idle
suspend. The screen, fan, and power LED turn off, but slp_s0_residency_usec
never increases. Hits 100% on affected hardware.
Error log on resume:
intel_pmc_core INT33A1:00: CPU did not enter SLP_S0!!! (S0ix cnt=0)
...
intel_pmc_core INT33A1:00: PMC0:GBE_PGD0_PG_STS 0
intel_pmc_core INT33A1:00: PMC0:GBE_D3_STS 0
intel_pmc_core INT33A1:00: PMC0:GBE_VNN_REQ_STS 0
intel_pmc_core INT33A1:00: PMC0:CPU_C10_REQ_STS 1
The CPU reaches C10, but the onboard GbE IP never power gates when K1 is
enabled.
An earlier S0ix failure mode on the same Dell hardware came from a
Realtek RTL8116AF add-in card (r8169 driver) and was fixed in LP:
#2160475. S0ix broke again after upstream commit 578294b8b60d ("e1000e:
Reconfigure PLL clock gate timeout and re-enable K1 on Meteor Lake",
upstream in v7.2, backported in LP: #2164666) re-enabled K1 by default
on Meteor Lake and newer platforms.
[Fix]
Add a DMI quirk entry for the affected Dell system to disable_k1_list in the
e1000e driver so K1 stays disabled by default. Fixes commit 578294b8b60d (v7.2).
Patch submitted upstream (under review on intel-wired-lan, not merged yet):
https://lore.kernel.org/intel-wired-lan/[email protected]/
[Test Plan]
1. Read S0ix residency before suspend:
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
2. Run 30 suspend cycles:
$ for i in $(seq 1 30); do sudo rtcwake -m mem -s 20; sleep 5; done
3. Check S0ix residency and dmesg after resume:
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
$ sudo dmesg | grep "CPU did not enter SLP_S0"
Without patch: slp_s0_residency_usec stays unchanged and dmesg prints "CPU did
not enter SLP_S0!!!" on every cycle.
With patch: slp_s0_residency_usec increases on every cycle and no SLP_S0 error
shows up in dmesg.
[Where problems could occur]
Affects the e1000e ethernet driver.
The change adds an exact DMI vendor and product match to
disable_k1_list, scoping the behavior change to one Dell machine.
Keeping K1 off prevents the PHY link from entering the K1 power-saving
state while active, which slightly raises ethernet link power use while
the system is awake. If the DMI string matched unintended Dell systems,
those machines would also disable K1 when awake; if it failed to match a
BIOS DMI variant of the target hardware, S0ix suspend would still fail.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: New
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Stonking)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Tenacious)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: New
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Stonking)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Tenacious)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Resolute)
Status: New => In Progress
** Changed in: linux (Ubuntu Stonking)
Status: New => In Progress
** Changed in: linux (Ubuntu Resolute)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Stonking)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Tenacious)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174973
Title:
Dell systems with Intel I219 ethernet fail to enter S0ix on suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174973/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs