From: Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>
To: David Mathog <mathog-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Save power at idle onTyan S2466N-MPX, athcool, etc.
Date: Wed, 05 Oct 2005 11:56:26 +0200 [thread overview]
Message-ID: <1128506186.4964.22.camel@localhost.localdomain> (raw)
In-Reply-To: <E1ELTUx-0001CZ-00-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
On Fri, 2005-09-30 at 15:36 -0700, David Mathog wrote:
> Flushed with success from that I next tried athcool
> on a single processor (athlon-MP 2200+) Tyan 2466N-MPX
> using a 2.6.8.1 kernel. No joy. It claimed to have
> changed the bits it controls but this didn't do a thing
> to the idle CPU temperature. Neither did turning those bits
> off, so it wasn't already in the low power state.
>
> This gives a pretty good clue why:
>
> % modprobe processor
> % cat /proc/acpi/processor/CPU0/info
> processor id: 0
> acpi id: 0
> bus mastering control: no
> power management: no
> throttling control: no
> limit interface: no
We had a discussion about exactly this a few weeks ago.
It boils down to: the AMD768 chipset can do C1/C2/C3 but not out of the
box using ACPI. First because ACPI processor support did not support
multiprocessor, now it does, but the ACPI parameters of this motherboard
prevent C2/C3 from being used by ACPI processor support.
So, out of the box you have C1, using the amd76x_pm you also have C2 and
optionally C3 support (although that completely screws up my sata
controller).
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2115 bytes --]
next prev parent reply other threads:[~2005-10-05 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 22:36 Save power at idle onTyan S2466N-MPX, athcool, etc David Mathog
[not found] ` <E1ELTUx-0001CZ-00-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.org>
2005-10-05 9:56 ` Erik Slagter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-02 18:29 David Mathog
2005-10-05 16:33 David Mathog
[not found] ` <E1ENCCr-0005rD-00-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.org>
2005-10-06 8:09 ` Erik Slagter
2005-10-06 20:54 David Mathog
[not found] ` <E1ENckb-0007Dh-00-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.org>
2005-10-07 9:21 ` Erik Slagter
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=1128506186.4964.22.camel@localhost.localdomain \
--to=erik-kw7pgp3xnp7a5ebddlwbiw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mathog-Mlb+9xX7RBA8OKIjkCRLjtKIQNXEaThN@public.gmane.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