Regression: unable to reach low idle states on Tiger Lake

[Kostadin Stoilov]

After upgrading to Ubuntu 24.04 the CPU is unable to hit lower idle states.

The device is a HP Spectre x360 14 (14-ea1000) with a Tiger Lake CPU.

This is a regression introduced somewhere 6.5.0-42 and 6.8.0-36. The issue is not observed when booting the same OS with 6.5.0-42.

Some debug output:

root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show
Package C2 : 36087003
Package C3 : 69314350
Package C6 : 0
Package C7 : 0
Package C8 : 0
Package C9 : 0
Package C10 : 0

$ sudo cat /sys/kernel/debug/pmc_core/substate_requirements
                       Element | S0i2.0 | Status |
pmc0: USB2PLL_OFF_STS | Required | Yes |
pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | |
pmc0: PCIe_Gen3PLL_OFF_STS | Required | Yes |
pmc0: OPIOPLL_OFF_STS | Required | Yes |
pmc0: OCPLL_OFF_STS | Required | Yes |
pmc0: MIPIPLL_OFF_STS | Required | Yes |
pmc0: AC_Ring_Osc_OFF_STS | Required | Yes |
pmc0: SATAPLL_OFF_STS | Required | Yes |
pmc0: CSME_PG_STS | Required | Yes |
pmc0: SATA_PG_STS | Required | Yes |
pmc0: xHCI_PG_STS | Required | Yes |
pmc0: UFSX2_PG_STS | Required | Yes |
pmc0: OTG_PG_STS | Required | Yes |
pmc0: SPA_PG_STS | Required | Yes |
pmc0: SPB_PG_STS | Required | Yes |
pmc0: SPC_PG_STS | Required | |
pmc0: THC0_PG_STS | Required | Yes |
pmc0: THC1_PG_STS | Required | Yes |
pmc0: GBETSN_PG_STS | Required | Yes |
pmc0: GBE_PG_STS | Required | Yes |
pmc0: LPSS_PG_STS | Required | Yes |
pmc0: xHCI0_D3_STS | Required | Yes |
pmc0: xDCI1_D3_STS | Required | Yes |
pmc0: IS_D3_STS | Required | Yes |
pmc0: GBE_TSN_D3_STS | Required | Yes |
pmc0: CPU_C10_REQ_STS_0 | Required | Yes |
pmc0: MPHY_Core_DL_REQ_STS_16 | Required | |
pmc0: Break-even_En_REQ_STS_17 | Required | Yes |
pmc0: Auto-demo_En_REQ_STS_18 | Required | Yes |
pmc0: Int_Timer_SS_Wake0_Pol_STS | Required | |
pmc0: Int_Timer_SS_Wake1_Pol_STS | Required | |
pmc0: Int_Timer_SS_Wake2_Pol_STS | Required | |
pmc0: Int_Timer_SS_Wake3_Pol_STS | Required | |
pmc0: Int_Timer_SS_Wake4_Pol_STS | Required | |
pmc0: Int_Timer_SS_Wake5_Pol_STS | Required | |

On 6.5:
pmc0: MPHY_Core_DL_REQ_STS_16 | Required | |
pmc0: SPC_PG_STS | Required | |
pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | |

have status set to 'Yes'

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/seq: kstoilov 2634 F.... pipewire
 /dev/snd/controlC0: kstoilov 2634 F.... pipewire
                      kstoilov 2641 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 10 21:26:37 2024
InstallationDate: Installed on 2023-05-04 (433 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
MachineType: HP HP Spectre x360 Convertible 14-ea1xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-38-generic N/A
 linux-backports-modules-6.8.0-38-generic N/A
 linux-firmware 20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-07-07 (3 days ago)
dmi.bios.date: 04/03/2024
dmi.bios.release: 15.33
dmi.bios.vendor: AMI
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 89DB
dmi.board.vendor: HP
dmi.board.version: 40.65
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 40.65
dmi.modalias: dmi:bvnAMI:bvrF.33:bd04/03/2024:br15.33:efr40.65:svnHP:pnHPSpectrex360Convertible14-ea1xxx:pvr:rvnHP:rn89DB:rvr40.65:cvnHP:ct31:cvrChassisVersion:sku457Q6AVT#ABA:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 14-ea1xxx
dmi.product.sku: 457Q6AVT#ABA
dmi.sys.vendor: HP

[AaronMa (mapengyu)]

@En-Wei

Could you check this issue and try to reproduce this issue if the hw is reachable?