All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Coretemp goes up since 2.6.31.4
Date: Sat, 10 Apr 2010 08:07:30 +0000	[thread overview]
Message-ID: <20100410100730.54776659@hyperion.delvare> (raw)
In-Reply-To: <20100409111733.7bb2b5fa@hyperion.delvare>

On Fri, 09 Apr 2010 20:08:18 +0200, dienet wrote:
> On Fri, 09 Apr 2010 11:17:33 +0200, Jean Delvare <khali@linux-fr.org>
> wrote:
> 
> > On Thu, 08 Apr 2010 18:36:34 +0200, dienet wrote:
> >> I was using 2.6.31.4 for quite some time - it works OK.
> >> Command 'sensor' that gives me temperature on my C2D, was saying that
> >> cores have around 28-45 deg (min and maxs on normal day work)
> >> Now on 2.6.33.1 sensors gives temperatures around 32-48 deg. I never  
> >> seen
> >> 29 or below. No room temperature is changing (got two kernels installed,
> >> so I can change it quickly)
> >> Who is telling the truth here? Was there any works on coretemp module
> >> since 2.6.31.4 that made the change in read-out?
> >
> > There were some changes to the coretemp driver in 2.6.32 and 2.6.33,
> > but these shouldn't affect older CPU models and would also not change
> > the readout by a few degrees. You can check if the high temperature
> > limit is the same - then you can assume the driver changes did not
> > affect your system.
> 
> On 2.6.31.4:
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +33.0°C  (high = +100.0°C, crit = +100.0°C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +33.0°C  (high = +100.0°C, crit = +100.0°C)
> 
> On 2.6.33.1:
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +34.0°C  (high = +105.0°C, crit = +105.0°C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +34.0°C  (high = +105.0°C, crit = +105.0°C)
> 
> So there is a 5 deg diffrance. I did not change any config files.

I assume these results are using the original coretemp driver of each
kernel. So, you are in one of these cases where the heuristic changes
in 2.6. I can't say whether this is correct in your case or not, this
heuristic is a horrible mess. But the relevant thing here is that your
CPU is actually running _cooler_ in 2.6.33 than in 2.6.31: 71 degrees
below the critical limit, instead of 67 degrees below the limit
previously. In both cases, you have a huge thermal margin, so it's
alright.

The fact that the high limit has the same value as the critical limit
is certainly a bug, as it doesn't make any sense physically.

> >> I think that because that temp. change fan is working more often.
> >>
> >> I'm using Lenovo ThinkPad T61.
> >
> > This suggests that the temperature increase is real and this isn't just
> > a reporting issue. I suggest that you check
> > in /proc/acpi/processor/*/power, the amount of time spent in C2 and C3
> > states. Also install powertop and run it on both kernels, see if 2.6.33
> > has more frequent wake-ups than 2.6.31.
> 
> On 2.6.31.4 powertop says:
> 
> C3 - 90, 7% of the time
> P (800MHz) - 98%
> Wakeups: 627
> 
> On 2.6.33.1 powertop says:
> 
> C3 - 93% of the time
> P (800MHz) - 98%
> Wakeups: 556

So 2.6.33 is indeed better, which is good news.

> Was running the same programs. Kernel 2.6.33.1 was running for about 1h.
> 
> I'm asuming that /proc/acpi/processor/*/power is used by powertop so I'm
> not paseting it. But it also says that C3 is more often used then others.


-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-04-10  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  9:17 [lm-sensors] Coretemp goes up since 2.6.31.4 Jean Delvare
2010-04-09 18:08 ` dienet
2010-04-10  8:07 ` Jean Delvare [this message]
2010-04-12 17:22 ` dienet
2010-04-12 19:11 ` Jean Delvare
2010-04-12 19:52 ` dienet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100410100730.54776659@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.