lkml.org 
[lkml]   [2011]   [Mar]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: intel_ips produces constant load of 1
Jesse Barnes wrote:
> On Mon, 21 Mar 2011 11:04:04 -0700
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
>>> ps aux | grep ips
>>> root 593 0.0 0.0 0 0 ? S 17:20 0:00
>>> [ips-adjust]
>>> root 594 0.0 0.0 0 0 ? D 17:20 0:00
>>> [ips-monitor]
>>>
>>> If the module isn't loaded, the load of the machine in idle mode is 0 as
>>> expected.
>>
>> This is a reporting problem, and probably due to the schedule() call
>> and associated task state in the ips-monitor thread. I thought setting
>> the task state to interruptible would prevent this, but it seems like
>> it's not enough for the deferrable on-stack timers?
>>
>> At any rate, it's not actually causing increased CPU usage, so you can
>> safely ignore it until we have a fix.
>
> Oops, one task uses interruptible correctly, but the monitor thread
> doesn't.
>
> Does this patch fix your load average?

The patch works fine:

ps aux | grep ips
root 22427 0.0 0.0 0 0 ? S 19:15 0:00
[ips-adjust]
root 22428 0.0 0.0 0 0 ? S 19:15 0:00
[ips-monitor]



btw: what does this mean (first line):


kernel: [ 6610.030205] intel ips 0000:00:1f.6: CPU TDP doesn't match
expected value (found 25, expected 29)
kernel: [ 6610.030218] intel ips 0000:00:1f.6: PCI INT C -> GSI 18
(level, low) -> IRQ 18
kernel: [ 6610.030733] intel ips 0000:00:1f.6: IPS driver initialized,
MCP temp limit 90


Thank you,
kind regards,
Andreas


\
 
 \ /
  Last update: 2011-03-25 19:25    [W:0.070 / U:10.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site