Hi all,
I did some more testing with the Opteron CPUs, and it seems there is some
defect in coreboot as it does not report the state P5. I attached the output of
"cpupower frequency-info" which I obtained on a 1x6220/64G configuration
running coreboot and running the vendor bios.
I also did some wattage measures using a new Brennenstuhl PM 231 watt meter for
my whole system. It seems like coreboot still has some flaw in this regards, as
I was able to reproduce the high power drain in idle with the 6220 processor as
well.
With the vendor bios:
2x6276, 128G => 90W idle, ~350W load
1x6276, 64G => 66W idle, 165W load
1x6220, 64G => 70W idle, 157W
With coreboot:
1x6220, 64G => 101W idle, 165W load
One thing I noticed is that when running coreboot the power state P5 seems
absent, while it's present when running the vendor bios. Could this be the
cause for the high power drain in idle? (even if I am not sure if the system
enters these states at all). Please see the logs attached.
If you compare the config of 1x6276 vs. 2x6276 it seems like there is just a
difference of 24W in idle and I am sure the memory also draws some power.
Therefore, I wonder how big the improvement could be by replacing the
6200-series CPUs by one of the power-optimized "warsaw" modules (6338P or
6370P). I could not find any figures about idle power consumption with these
CPUs so I welcome any reports from others. I don't really need all that CPU
power but I would really like to use all of my 128G memory - which is why I am
looking for the most power efficient CPU for the KGPE-D16.
Cheers, Daniel
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 5.0 us
hardware limits: 1.40 GHz - 3.00 GHz
available frequency steps: 3.00 GHz, 2.60 GHz, 2.20 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: userspace powersave conservative ondemand
performance schedutil
current policy: frequency should be within 1.40 GHz and 3.00 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: 1.40 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes
Boost States: 2
Total States: 7
Pstate-Pb0: 3600MHz (boost state)
Pstate-Pb1: 3300MHz (boost state)
Pstate-P0: 3000MHz
Pstate-P1: 2600MHz
Pstate-P2: 2200MHz
Pstate-P3: 1800MHz
Pstate-P4: 1400MHz
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 5.0 us
hardware limits: 1.40 GHz - 3.00 GHz
available frequency steps: 3.00 GHz, 2.60 GHz, 2.20 GHz, 1.80 GHz, 1.40 GHz
available cpufreq governors: userspace powersave conservative ondemand
performance schedutil
current policy: frequency should be within 1.40 GHz and 3.00 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: 1.40 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes
Boost States: 2
Total States: 8
Pstate-Pb0: 3600MHz (boost state)
Pstate-Pb1: 3300MHz (boost state)
Pstate-P0: 3000MHz
Pstate-P1: 2600MHz
Pstate-P2: 2200MHz
Pstate-P3: 1800MHz
Pstate-P4: 1400MHz
Pstate-P5: 500MHz
--
coreboot mailing list: [email protected]
https://mail.coreboot.org/mailman/listinfo/coreboot
