Hi,
I just compiled and flashed the lastest master on my KGPE-D16 with pretty much the default config. My board has only one of the CPU sockets populated with an Opteron 6276. Things seem to work fine so far, except the power consumption. The "sensors" command reports a CPU power consumption of about ~85W (!) in idle:
--- k10temp-pci-00cb Adapter: PCI adapter temp1: +21.2°C (high = +70.0°C)
fam15h_power-pci-00c4 Adapter: PCI adapter power1: 85.13 W (crit = 115.11 W)
nouveau-pci-0500 Adapter: PCI adapter GPU core: +1.01 V (min = +0.60 V, max = +1.20 V) fan1: 0 RPM temp1: +37.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C)
k10temp-pci-00c3 Adapter: PCI adapter temp1: +24.1°C (high = +70.0°C) ---
With the vendor bios, the power consumption reported by "sensors" was just about the half - around 43W. I measured the consumption also on the power socket, and the whole systems seems to draw around 91W in idle (which is strange, since the GPU + hard drives + fans certainly don't take only 6W, but yeah...). Anyways, with the vendor bios, the power consumption of the whole system was around 60W (tested with a different power supply, but as a rough measure I guess this is representative).
In coreboot's menuconfig, I can't select any power saving options or such as it was possible for other boards, which leaves me a bit puzzled.
Anyone having simular issues?
Cheers, Daniel
On 02/09/2017 06:46 PM, Daniel Kulesz via coreboot wrote:
Hi,
I just compiled and flashed the lastest master on my KGPE-D16 with pretty much the default config. My board has only one of the CPU sockets populated with an Opteron 6276. Things seem to work fine so far, except the power consumption. The "sensors" command reports a CPU power consumption of about ~85W (!) in idle:
k10temp-pci-00cb Adapter: PCI adapter temp1: +21.2°C (high = +70.0°C)
fam15h_power-pci-00c4 Adapter: PCI adapter power1: 85.13 W (crit = 115.11 W)
nouveau-pci-0500 Adapter: PCI adapter GPU core: +1.01 V (min = +0.60 V, max = +1.20 V) fan1: 0 RPM temp1: +37.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C)
k10temp-pci-00c3 Adapter: PCI adapter temp1: +24.1°C (high = +70.0°C)
With the vendor bios, the power consumption reported by "sensors" was just about the half - around 43W. I measured the consumption also on the power socket, and the whole systems seems to draw around 91W in idle (which is strange, since the GPU + hard drives + fans certainly don't take only 6W, but yeah...). Anyways, with the vendor bios, the power consumption of the whole system was around 60W (tested with a different power supply, but as a rough measure I guess this is representative).
In coreboot's menuconfig, I can't select any power saving options or such as it was possible for other boards, which leaves me a bit puzzled.
Anyone having simular issues?
Cheers, Daniel
I am not. What does "cpufrequency monitor" report?
On Fri, 10 Feb 2017 00:37:57 -0500 "Taiidan@gmx.com" Taiidan@gmx.com wrote:
On 02/09/2017 06:46 PM, Daniel Kulesz via coreboot wrote:
Hi,
I just compiled and flashed the lastest master on my KGPE-D16 with pretty much the default config. My board has only one of the CPU sockets populated with an Opteron 6276. Things seem to work fine so far, except the power consumption. The "sensors" command reports a CPU power consumption of about ~85W (!) in idle:
k10temp-pci-00cb Adapter: PCI adapter temp1: +21.2°C (high = +70.0°C)
fam15h_power-pci-00c4 Adapter: PCI adapter power1: 85.13 W (crit = 115.11 W)
nouveau-pci-0500 Adapter: PCI adapter GPU core: +1.01 V (min = +0.60 V, max = +1.20 V) fan1: 0 RPM temp1: +37.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C)
k10temp-pci-00c3 Adapter: PCI adapter temp1: +24.1°C (high = +70.0°C)
With the vendor bios, the power consumption reported by "sensors" was just about the half - around 43W. I measured the consumption also on the power socket, and the whole systems seems to draw around 91W in idle (which is strange, since the GPU + hard drives + fans certainly don't take only 6W, but yeah...). Anyways, with the vendor bios, the power consumption of the whole system was around 60W (tested with a different power supply, but as a rough measure I guess this is representative).
In coreboot's menuconfig, I can't select any power saving options or such as it was possible for other boards, which leaves me a bit puzzled.
Anyone having simular issues?
Cheers, Daniel
I am not.
Thanks. May I ask which CPU you are using?
What does "cpufrequency monitor" report?
Here's the output of "cpufreq-info":
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. 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 - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.80%, 2.10 GHz:0.46%, 1.80 GHz:0.70%, 1.60 GHz:1.68%, 1.40 GHz:96.37% (736) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.54%, 2.10 GHz:0.08%, 1.80 GHz:0.29%, 1.60 GHz:3.19%, 1.40 GHz:95.91% (223) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.45%, 2.10 GHz:0.18%, 1.80 GHz:1.01%, 1.60 GHz:2.10%, 1.40 GHz:96.25% (445) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:1.95%, 2.10 GHz:0.22%, 1.80 GHz:1.16%, 1.60 GHz:1.78%, 1.40 GHz:94.89% (241) analyzing CPU 4: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.82%, 2.10 GHz:0.18%, 1.80 GHz:0.86%, 1.60 GHz:2.01%, 1.40 GHz:96.13% (448) analyzing CPU 5: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.43%, 2.10 GHz:0.09%, 1.80 GHz:0.24%, 1.60 GHz:4.50%, 1.40 GHz:94.75% (260) analyzing CPU 6: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:1.58%, 2.10 GHz:0.13%, 1.80 GHz:0.42%, 1.60 GHz:2.85%, 1.40 GHz:95.02% (433) analyzing CPU 7: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.30%, 2.10 GHz:0.06%, 1.80 GHz:0.27%, 1.60 GHz:4.67%, 1.40 GHz:94.70% (231) analyzing CPU 8: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 8 CPUs which need to have their frequency coordinated by software: 8 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.54%, 2.10 GHz:0.27%, 1.80 GHz:0.35%, 1.60 GHz:0.94%, 1.40 GHz:97.90% (331) analyzing CPU 9: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 9 CPUs which need to have their frequency coordinated by software: 9 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.29%, 2.10 GHz:0.09%, 1.80 GHz:0.14%, 1.60 GHz:0.37%, 1.40 GHz:99.11% (141) analyzing CPU 10: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 10 CPUs which need to have their frequency coordinated by software: 10 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.42%, 2.10 GHz:0.15%, 1.80 GHz:0.39%, 1.60 GHz:0.77%, 1.40 GHz:98.27% (273) analyzing CPU 11: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 11 CPUs which need to have their frequency coordinated by software: 11 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.09%, 2.10 GHz:0.09%, 1.80 GHz:0.18%, 1.60 GHz:0.25%, 1.40 GHz:99.38% (144) analyzing CPU 12: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 12 CPUs which need to have their frequency coordinated by software: 12 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.23%, 2.10 GHz:0.28%, 1.80 GHz:0.28%, 1.60 GHz:0.46%, 1.40 GHz:98.75% (277) analyzing CPU 13: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 13 CPUs which need to have their frequency coordinated by software: 13 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.44%, 2.10 GHz:0.17%, 1.80 GHz:0.10%, 1.60 GHz:0.33%, 1.40 GHz:98.97% (126) analyzing CPU 14: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 14 CPUs which need to have their frequency coordinated by software: 14 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.36%, 2.10 GHz:0.15%, 1.80 GHz:0.59%, 1.60 GHz:0.90%, 1.40 GHz:98.00% (257) analyzing CPU 15: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 15 CPUs which need to have their frequency coordinated by software: 15 maximum transition latency: 5.0 us. hardware limits: 1.40 GHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.10 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance, schedutil current policy: frequency should be within 1.40 GHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.40 GHz. cpufreq stats: 2.30 GHz:0.07%, 2.10 GHz:0.10%, 1.80 GHz:0.12%, 1.60 GHz:0.27%, 1.40 GHz:99.44% (121)
-
Daniel Kulesz -
Taiidan＠gmx.com