OEM Priority Project

No SYS%LPI residency in suspend when ethernet is connected

Bug #1962731 reported by Kai-Chuan Hsieh on 2022-03-02

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OEM Priority Project	New	Undecided	Unassigned
	linux-signed-oem-5.14 (Ubuntu)	Incomplete	Undecided	koba

Bug Description

Try the command

# turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15
...
Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI
9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00

There is no SYS%LPI residency.
Unplug ethernet, the residency become

Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI
8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82

The ethernet controller is I219-LM.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26
ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21
Uname: Linux 5.14.0-1024-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 2 05:24:51 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92
InstallationDate: Installed on 2021-11-03 (118 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-5.14
UpgradeStatus: No upgrade log present (probably fresh install)

See original description

Tags:

Revision history for this message

Kai-Chuan Hsieh (kchsieh) wrote on 2022-03-02:

Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.8 KiB, text/plain; charset="utf-8")

description:

updated

Revision history for this message

Kai-Chuan Hsieh (kchsieh) wrote on 2022-03-02:

sosreport-u-Latitude-5521-1962731-2022-03-02-drddnma.tar.xz Edit (4.8 MiB, application/x-tar)

Upload sos report.

summary:

- No SYS%LPI residency after a suspend/resume when ethernet connected
+ No SYS%LPI residency in suspend when ethernet is connected

Dirk Su (dirksu) on 2022-03-04

tags:

added: oem-priority originate-from-1954400 somerville

koba (kobako) on 2022-03-07

Changed in linux-signed-oem-5.14 (Ubuntu):
assignee:	nobody → koba (kobako)

Revision history for this message

koba (kobako) wrote on 2022-04-14 (last edit on 2022-04-14):

Screenshot from 2022-04-14 17-07-30.png Edit (273.6 KiB, image/png)

On cinnamo bay 16, With 5.14-oem-1032 and i219's lan connected,
PHM show PCIeLPM always L1 and GBE is on.
here's phm screen shot,

Revision history for this message

koba (kobako) wrote on 2022-04-14:

dmesg_202204141708 Edit (123.5 KiB, text/html)

Changed in linux-signed-oem-5.14 (Ubuntu):
status:	New → In Progress

Revision history for this message

koba (kobako) wrote on 2022-04-14 (last edit on 2022-04-14):

with 518rc1, there would encounter e1000e hang issue, even this patch has landed since 5.17rc7.
git tag --contains 1866aa0d0d
v5.17
v5.17-rc7
v5.17-rc8
v5.18-rc1
v5.18-rc2
~~~

Need Intel's help to figure out the hang issue and i219-lm power performance issue.

Revision history for this message

koba (kobako) wrote on 2022-04-14:

dmesg_518rc1_202204141714 Edit (102.5 KiB, text/html)

Changed in linux-signed-oem-5.14 (Ubuntu):
status:	In Progress → Incomplete

Revision history for this message

koba (kobako) wrote on 2022-04-14:

lspci_202204142303 Edit (78.1 KiB, text/plain)

Revision history for this message

koba (kobako) wrote on 2022-05-19:

the root cause is the i219-lm keeps the link up during suspend.
Is there a requirement that ethernet links must be down during suspend?

Revision history for this message

Kai-Chuan Hsieh (kchsieh) wrote on 2022-05-19:

If the platform estar8 passed, then it is okay. if not, if might be an issue that increase power consumption.

Revision history for this message

koba (kobako) wrote on 2022-05-19:

#10

@KC, do you know if the ethernet presents during estar assessment?
If ethernet is not essential, estar may be passed.

Revision history for this message

Kai-Chuan Hsieh (kchsieh) wrote on 2022-05-19:

#11

The ethernet needs to be connected during the test. Not all platforms are failed. I think it is still an issue that ethernet should not block CPU be in low power idle, but it doesn't block anything at the moment.