Z890 Pacakge C-states deeper than C2£

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   The below was copied from the support request form, 30 minutes after the expected automated email failed to arrive:

Hardware:

Board: ASRock Z890 Pro-A Wifi
CPU: Intel Core Ultra 7 265K
RAM: Crucial cp2k24g60c48u5 2x24 6000C48 @1.1V
Disk: 120 GB Inland Professional SSD
PSU: Antec Neo Eco 620C PSU

What BIOS option(s) do I need to set to allow the CPU to enter deep idle?

Turbostat reports that package sleep states deeper than the shallowest C2 are never used, and also, "MSR_PKG_CST_CONFIG_CONTROL: 0x00008002 (locked, pkg-cstate-limit=2 (pc3))", which is certainly suggestive. As far as I can tell, this platform is supposed to support also C3, C6, C8, and C10.

I've tried a bunch of different options that seem power-saving-related: all the ASPM and ALPM BIOS option set to least-power, "power floor management" in the CPU OC options set to Disabled, and nothing plugged in but a single SATA SSD. Nothing I can find changes that limit or results in any package c-state residency below C2.

The only thing that moves the wall power at all from 29 W is System Agent Geyserville, but that also underclocked the RAM to 5600, and it only shaves 3W. I understand that older, non-resonant-LLC PSUs can be less efficient at low load, but the package power is also 8 W (higher than my old Haswell) and the chipset heatsink stays noticeably warm.

I even tried Windows, which is actually a little worse, at 30 W from the wall.

Please help. I have seen posts on Reddit and AskUbuntu from people having similar problems with older chipsets, using an AMISCE Windows utility to change unexposed BIOS settings. But, I don't want to risk a bricking, and even if that worked I wouldn't want to have to do it again every time there's a BIOS update.

My preferred outcome is that the setting that people are modding with AMISCE become available in the public BIOS release, so that less "enthusiastic" owners can benefit. I've spent way more time chasing this down than the electricity would cost already, and I'd like the result to be multiplied.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Yump Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 21 Dec 2024 Status: Offline Points: 20	Post Options Post Reply Quote Yump Report Post Thanks(0) Quote Reply Topic: Z890 Pacakge C-states deeper than C2£ Posted: 5 hours 54 minutes ago at 11:08am
	The below was copied from the support request form, 30 minutes after the expected automated email failed to arrive: Hardware: Board: ASRock Z890 Pro-A Wifi CPU: Intel Core Ultra 7 265K RAM: Crucial cp2k24g60c48u5 2x24 6000C48 @1.1V Disk: 120 GB Inland Professional SSD PSU: Antec Neo Eco 620C PSU What BIOS option(s) do I need to set to allow the CPU to enter deep idle? Turbostat reports that package sleep states deeper than the shallowest C2 are never used, and also, "MSR_PKG_CST_CONFIG_CONTROL: 0x00008002 (locked, pkg-cstate-limit=2 (pc3))", which is certainly suggestive. As far as I can tell, this platform is supposed to support also C3, C6, C8, and C10. I've tried a bunch of different options that seem power-saving-related: all the ASPM and ALPM BIOS option set to least-power, "power floor management" in the CPU OC options set to Disabled, and nothing plugged in but a single SATA SSD. Nothing I can find changes that limit or results in any package c-state residency below C2. The only thing that moves the wall power at all from 29 W is System Agent Geyserville, but that also underclocked the RAM to 5600, and it only shaves 3W. I understand that older, non-resonant-LLC PSUs can be less efficient at low load, but the package power is also 8 W (higher than my old Haswell) and the chipset heatsink stays noticeably warm. I even tried Windows, which is actually a little worse, at 30 W from the wall. Please help. I have seen posts on Reddit and AskUbuntu from people having similar problems with older chipsets, using an AMISCE Windows utility to change unexposed BIOS settings. But, I don't want to risk a bricking, and even if that worked I wouldn't want to have to do it again every time there's a BIOS update. My preferred outcome is that the setting that people are modding with AMISCE become available in the public BIOS release, so that less "enthusiastic" owners can benefit. I've spent way more time chasing this down than the electricity would cost already, and I'd like the result to be multiplied.