From: Joerg Sommrey <jo@sommrey.de>
To: psavo@iki.fi, Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: High CPU temp on Athlon MP w/ recent 2.6 kernels
Date: Wed, 7 Apr 2004 20:14:41 +0200 [thread overview]
Message-ID: <200404071814.i37IEf2o005602@bear.sommrey.de> (raw)
In-Reply-To: <1I8kJ-3Z8-1@gated-at.bofh.it>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
In linux.kernel you write:
>At least on A7M266-D lmsensors read thermal sensors very wrong. I
>haven't got time to contact devs with that, but I do know for sure that
>amd76x_pm really does make cooling calls, even in 2.6.5-rc3-mm3
>(There should be /sys/devices/pci0000\:00/0000\:00\:00.0/C2_cnt file,
>which tells how many times has amd76x_pm really made the disconnection call).
lmsensors might be correct here as there is a sample config from Tyan
for my board. C2_cnt shows that amd76x_pm is indeed working.
Otherwise I had expected a much higher temperature.
>One issue is that from some kernel version amd76x_pm's idle() is called
>upto 3.5x times more often when there's some audio activity. So in
>effect number of calls to default_idle() jumps from 1100Hz to 3800Hz.
>(this is reproducible with 'rhytmbox' -application, but not with xmms.
>AFAIK my xmms uses OSS emulation and rhytmbox is native alsa.)
>Ahem. Could you actually try:
>echo 3 > /sys/devices/pci0000\:00/0000\:00\:00.0/lazy_idle
Did that.
>This could help gaining 5-8°C. HZ changed from 100 to 1000 in 2.6, so
>amd76x_pm old default doesn't apply overly well here.
Bingo! Currently running 2.6.5-mm1 at 42.0/43.5°C!
>There's some funniness going on with this tunable. It doesn't really
>affect how many times/second we call amd76x_pm.idle(), but rather how
>easily we go into sleep (no sleep if both CPU's aren't idle).
>With lazy_idle at 3 I get bad distortions with bttv card. with 3000 they
>disappear, but so does the thermal throttling :)
>(Sorry for lack of coherence right now)
Wouldn't be a bad idea to document this :-)
Thanks!
-jo
--
-rw-r--r-- 1 jo users 80 2004-04-07 19:37 /home/jo/.signature
next parent reply other threads:[~2004-04-07 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1I4Ka-10u-5@gated-at.bofh.it>
[not found] ` <1I5n5-1A2-41@gated-at.bofh.it>
[not found] ` <1I5Gl-1OD-33@gated-at.bofh.it>
[not found] ` <1I8kJ-3Z8-1@gated-at.bofh.it>
2004-04-07 18:14 ` Joerg Sommrey [this message]
2004-04-06 19:36 Joerg Sommrey
2004-04-06 20:26 ` Gene Heskett
2004-04-06 20:45 ` Joerg Sommrey
2004-04-06 21:57 ` Gene Heskett
2004-04-07 16:17 ` Joerg Sommrey
2004-04-06 23:27 ` Pasi Savolainen
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=200404071814.i37IEf2o005602@bear.sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psavo@iki.fi \
/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
Powered by JetHome