While executing the tools on target tests we discovered an issue when executing the "powertop --calibrate" command. Basically, after the calibration starts and a few steps are finished the calibration sequence freezes at the following step: "Calibrating: CPU wakeup power consumption". root@qemuppc:~# powertop --calibrate Cannot load from file /var/cache/powertop/saved_results.powertop Cannot load from file /var/cache/powertop/saved_parameters.powertop RAPL device for cpu 0 Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). RAPL device for cpu 0 Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR). Cannot load from file /var/cache/powertop/saved_parameters.powertop Starting PowerTOP power estimate calibration Calibrating idle function ktime_to_ns not defined Calibrating: disk usage Calibrating backlight Calibrating idle Calibrating: CPU usage on 1 threads Calibrating: CPU usage on 4 threads Calibrating: CPU wakeup power consumption Calibrating: CPU wakeup power consumption Calibrating: CPU wakeup power consumption If the calibration process is stopped (ctrl+c) the target behaves strangely: it either freezes or it takes a lot of times to run any command (other tests may fail, like perf --time=x if the target is used after the calibration issue).
Test object: 1.6_M5_RC2:3e528d3e4bc542ca2f654c54363c56af0fb9f61b Test target: qemuPPC Test host: Ubuntu 12.04
This works correctly for 3.10, but fails 3.14
poky: commit 50067e069c8cbc0d339819494f22ae7623d47aa6 branch : master The issue can not be reproduced on qemuppc.
poky: commit 50067e069c8cbc0d339819494f22ae7623d47aa6 branch : master The issue can not be reproduced on qemuppc
We have encountered this issue again when testing Yocto 1.7 M1 RC1 (poky 68824d9b8f6e290da078383316b3f4b732585f2b).
poky: commit 67261e2d7a2acd2646b4e25ab1456bec07e93834 branch : master The issue can not be reproduced on qemuppc.
Catalin, can you verify this? Thanks, Alex.
This bug is fixed. Verified on yocto-1.8_M2.rc1 and this issue is no longer reproducible. Poky: commit d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b Target: QemuPPC Test Host: Ubuntu 14.04 LTS