Description of problem: The C-state info from acpitool -c does not match what's in /proc/acpi/processor/CPU[n]/power Version-Release number of selected component (if applicable): acpitool-0.5.1-1.fc12.x86_64 How reproducible: always Steps to Reproduce: 1.run acpitool -c 2.run `cat /proc/acpi/processor/CPU0/power` Actual results: /proc data shows mostly C1 state ussage, acpitool shows none: # cat /proc/acpi/processor/CPU0/power active state: C0 max_cstate: C8 maximum allowed latency: 2000000000 usec states: C1: type[C1] promotion[--] demotion[--] latency[000] usage[13456304] duration[00000000000000000000] C2: type[C2] promotion[--] demotion[--] latency[005] usage[00000000] duration[00000000000000000000] C3: type[C3] promotion[--] demotion[--] latency[020] usage[00000000] duration[00000000000000000000] # acpitool -c CPU type : Dual-Core AMD Opteron(tm) Processor 1210 Min/Max frequency : 1000/1800 MHz Current frequency : 1000 MHz Frequency governor : ondemand Freq. scaling driver : powernow-k8 Cache size : 1024 KB Bogomips : 2000.17 Bogomips : 2000.17 # of CPU's found : 2 Processor ID : 0 Bus mastering control : yes Power management : yes Throttling control : no Limit interface : no Active C-state : C0 C-states (incl. C0) : 3 Usage of state C1 : 0 (0.0 %) Usage of state C2 : 0 (0.0 %) Processor ID : 1 Bus mastering control : yes Power management : yes Throttling control : no Limit interface : no Active C-state : C0 C-states (incl. C0) : 3 Usage of state C1 : 0 (0.0 %) Usage of state C2 : 0 (0.0 %) Expected results: values consistent
This is something that needs to be reported to the upstream developers. Please report it at http://freeunix.dyndns.org:8000/site2/acpitool.shtml Thanks
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers