From: Marc Singer <elf@buici.com>
To: cpufreq@www.linux.org.uk
Subject: Re: Athlon 64 complains of frequency mismatch
Date: Tue, 22 Jun 2004 10:59:05 -0700 [thread overview]
Message-ID: <20040622175905.GA17408@buici.com> (raw)
In-Reply-To: <20040622171103.GB8111@dominikbrodowski.de>
On Tue, Jun 22, 2004 at 07:11:03PM +0200, Dominik Brodowski wrote:
> Also, are there any entries in the BIOS you can toggle which might be
> related to "Cool&Quiet", "PnP-capable OS", ...?
Bingo. There is a Cool&Quiet enable option. The dump module now
produces this:
ACPI: Processor [CPU1] (supports C1, 16 throttling states)
number of states: 10
acpi_pdump: P0: 2000 MHz, 89000 mW, 125 uS s:0x8c c:0xa020288c
acpi_pdump: P1: 1800 MHz, 66000 mW, 125 uS s:0x18a c:0xa020298a
acpi_pdump: P2: 1800 MHz, 66000 mW, 125 uS s:0x18a c:0xa020298a
acpi_pdump: P3: 1800 MHz, 66000 mW, 125 uS s:0x18a c:0xa020298a
acpi_pdump: P4: 1800 MHz, 66000 mW, 125 uS s:0x18a c:0xa020298a
acpi_pdump: P5: 800 MHz, 35000 mW, 125 uS s:0x280 c:0xa0202a80
acpi_pdump: P6: 800 MHz, 35000 mW, 125 uS s:0x280 c:0xa0202a80
acpi_pdump: P7: 800 MHz, 35000 mW, 125 uS s:0x280 c:0xa0202a80
acpi_pdump: P8: 800 MHz, 35000 mW, 125 uS s:0x280 c:0xa0202a80
acpi_pdump: P9: 800 MHz, 35000 mW, 125 uS s:0x280 c:0xa0202a80
control_register:
130 12 127 0 0 0 0
status_register:
130 12 127 0 0 0 0
And the powernow-p8 driver loads.
Perhaps this is an addition to the FAQ:
Q609: AMD Cool&Quiet CPU won't load the powernow-k? driver. Why?
A609: The powernow driver gets it's information about processor
states from the BIOS's reported ACPI control data. If the
powernow driver won't load it may be because Cool&Quiet hasn't
been enabled in the BIOS. Make sure that BIOS settings for a
PowerNow or a Cool&Quiet option are enabled.
Or, maybe the driver should output a kernel message about BIOS
settings.
Cheers.
next prev parent reply other threads:[~2004-06-22 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 18:51 Athlon 64 complains of frequency mismatch Marc Singer
2004-06-19 10:44 ` Dominik Brodowski
2004-06-19 15:55 ` Marc Singer
2004-06-19 16:36 ` Marc Singer
2004-06-21 20:26 ` Dominik Brodowski
2004-06-21 21:42 ` Marc Singer
2004-06-22 17:11 ` Dominik Brodowski
2004-06-22 17:59 ` Marc Singer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 6:02 paul.devriendt
2004-06-22 7:30 ` Arjan van de Ven
2004-06-22 10:28 ` Andi Kleen
2004-06-22 15:16 ` Marc Singer
2004-06-22 15:26 paul.devriendt
2004-06-22 16:07 ` Marc Singer
2004-06-22 17:07 ` Dominik Brodowski
2004-06-22 15:28 paul.devriendt
2004-06-23 7:43 paul.devriendt
2004-06-23 17:52 ` Len Brown
2004-06-23 7:43 paul.devriendt
2004-06-23 7:54 ` Marc Singer
2004-06-23 8:07 paul.devriendt
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=20040622175905.GA17408@buici.com \
--to=elf@buici.com \
--cc=cpufreq@www.linux.org.uk \
/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