From: valvoline <valvoline@vrlteam.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: temp.c and cputable.c issues
Date: Wed, 14 Jan 2004 20:39:10 +0100 [thread overview]
Message-ID: <20040114193910.GN2658@adapter.n0skillz.org> (raw)
hi folks!,
i'm running the last stable kernel tree with benh r1 patches (2.6.1-r1 under gentoo).
i've enabled TAU and CPUFREQ, and compiled everything...all seems to go well,
but looking into a dmesg from kernel i'm receiving this message:
...
Thermal assist unit not available
...
looking into /usr/src/linux/arch/ppc/kernel/cputable.c i've noticed that all
7455 based machine, have the CPU_FTR_TAU feature disabled, so i've patched the
file as in the included patch...now all seems to works fine!.
cputemperature is shown in /proc/cpuinfo, and all the infos seems to be
good calibrated and really near to real-world values.
Actually, i'm writing a dockapp for wm, and i've noticed some troubles in temperature;
after put my cpu to low-power with an:
'echo -n "0:600000:600000:performance" > /proc/cpufreq'
the value temperature in /proc/cpuinfo start to grow-up with NOSENSE...seems
that every 1sec-tick, the temperature value (both high and low) increment of
1 unit...at 68°-69° stop is race and the value remain at this point with
further changes; no matter if the cpuload is 0% or 100%...the value is
completely stalled.
If i restore the cpu to high-power with an:
'echo -n "0:900000:900000:performance" > /proc/cpufreq'
the temperature in /proc/cpuinfo start to grow down, and the values returns
to be correctly and with a real-life attinency.
Looking into sources under /usr/src/linux/arch/ppc/kernel/temp.c, i've
investigated around the lines concerning the TAU_update, and seems that
the double-if above:
...
if((thrm = mfspr(SPRN_THRM2)) & THRM1_TIV){ /* is valid? */
if(thrm & THRM1_TIN){ /* crossed high threshold */
...
after switching down the cpu-freq, is every true!
I think that the problem is in interrupts enabling/disabling during the
'cpu_set_speed' function into pmac_cpufreq.c, but i've no ideas on howto check
it...perhaps some guru, can give a more comprensive answer.
any suggests/comments, are welcome,
regards
--
[ valvoline :: VRL Team :: s0ftpj :: freaknet Medialab :: GPG key available ]
[ key fingerprint :: - :: B7E2 48BC 705F AE8F 9ABE E422 076A 2561 1D67 B4DD ]
[ GPG key available on keyserver :: pgp.mit.edu :: with keyID :: 1D67B4DD :: ]
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-14 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 19:39 valvoline [this message]
2004-01-14 22:10 ` temp.c and cputable.c issues Tom Rini
2004-01-14 20:11 ` valvoline
2004-01-14 22:38 ` Tom Rini
2004-01-15 8:19 ` Colin Leroy
2004-01-15 7:03 ` valvoline
2004-01-15 7:16 ` valvoline
2004-01-15 9:32 ` Colin Leroy
2004-01-16 7:02 ` valvoline
2004-01-16 10:21 ` Colin Leroy
2004-01-16 11:10 ` Geert Uytterhoeven
2004-01-16 11:26 ` Colin Leroy
2004-01-15 7:20 ` valvoline
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 9:38 Colin Leroy
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=20040114193910.GN2658@adapter.n0skillz.org \
--to=valvoline@vrlteam.org \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).