From: dienet <dienet@poczta.fm>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Coretemp goes up since 2.6.31.4
Date: Mon, 12 Apr 2010 17:22:22 +0000 [thread overview]
Message-ID: <op.va17vj19wcw97g@localhost> (raw)
In-Reply-To: <20100409111733.7bb2b5fa@hyperion.delvare>
On Sat, 10 Apr 2010 10:07:30 +0200, Jean Delvare <khali@linux-fr.org>
wrote:
> 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.
I'm just saying what I see. And I see that sensors show higher temp. on
2.6.33 then on 2.6.31 - that's all I can say.
Now I'm on 2.6.33.2 and I never see 30 deg. or below. On 2.6.31 30 deg. or
below was quite normal (but I don't know if that was the *real* temp).
> 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.
Any way to fix it? I can say that this bug is quite old or my system isn't
configured for a long time.
> So 2.6.33 is indeed better, which is good news.
I'll say that after longger work. 1h is nothing, and there is a big margin
of error.
--
pozdr0
dienet
"Old C programmers never die. They're just cast into void."
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-04-12 17:22 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
2010-04-12 17:22 ` dienet [this message]
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=op.va17vj19wcw97g@localhost \
--to=dienet@poczta.fm \
--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.