[indiana-discuss] b111a: Power Management and nwam-issue ?

[Łukasz Grąbczewski]

same for me: event-mode makes my Intel Atom 100% time at 1600MHz while
poll-mode works flawlessly (at 800MHz at idle and quite rapidly
switching to higher clock rates when on load).

Cheers
LG


2009/4/27 Yiannis Mavroukakis <imavroukakis at gameaccount.com>:
> Hmm no that wasn't it..when I switched to poll-mode however, it worked.
>
> Aubrey Li wrote:
>>
>> On Sun, Apr 26, 2009 at 1:27 AM, Ioannis Mavroukakis
>> <imavroukakis at gameaccount.com> wrote:
>>
>>>
>>> Hmm running powertop shows my cpu pegged at warp speed
>>>
>>>          OpenSolaris PowerTOP version 1.1
>>>
>>> Cn            Avg    residency    P-states (frequencies)
>>> C0 (cpu    running)        (32.7%)         800 Mhz    0.0%
>>> C1            0.6ms    (67.3%)        1200 Mhz    0.0%
>>>                                              1600 Mhz    0.0%
>>>                                              2000 Mhz    0.0%
>>>                                              2001 Mhz(turbo)    100.0%
>>>
>>
>> if your system is idle, C0 residency should < 10%.
>> Here C0 = 32.7%, there must be a workload on the system.
>>
>>
>>>
>>> Wakeups-from-idle per second: 1156.3    interval: 5.2s
>>> Power usage (ACPI estimate): 2.737W (discharging: 0.6 hours)
>>>
>>> Top causes for wakeups:
>>> 19.3% (223.2)               <kernel> :    genunix`cv_wakeup
>>> 8.6% (100.0)               <kernel> :    genunix`clock
>>>
>>
>> Apparantly, clock should be the top cause for wakeups, not cv_wakeup
>> if your system is in idle.
>>
>>
>>>
>>> 4.0% ( 46.3)            <interrupt> :    i915#0
>>> 3.5% ( 40.8)               sched :    <cross calls>
>>> 3.2% (    36.9)         <interrupt> :    i8042#0
>>> 1.9% (    21.9)            <interrupt> :    wpi#0
>>> 1.7% (    19.2)               <kernel> :
>>>  uhci`uhci_handle_root_hub_status_change
>>>
>>>
>>>
>>> Q - Quit   R - Refresh
>>>
>>> I have cpupm and cpu-threshold setup...it used to work on my Travelmate
>>> 5720, not any more after svn111..
>>>
>>
>> You can check the system by "mpstat" or "vmstat" or "prstat" to see the
>> cpu
>> utilization and what is using CPU.
>>