From: Andi Kleen <andi@firstfloor.org>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: S K <nospamnoham@gmail.com>, Thomas Renninger <trenn@suse.de>,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Mon, 11 Aug 2008 12:55:11 +0200 [thread overview]
Message-ID: <874p5r3jow.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1218432270.6671.75.camel@yakui_zhao.sh.intel.com> (Zhao Yakui's message of "Mon, 11 Aug 2008 13:24:30 +0800")
Zhao Yakui <yakui.zhao@intel.com> writes:
> On Sun, 2008-08-10 at 21:44 -0700, S K wrote:
>> >> So I'm guessing this is a kernel bug.
>> > >From the attached acpidump it seems that there is no definition of
>> > _PCT,_PSS, _PPC. So acpi_cpufreq driver can't be used on your machine.
>> > This is a BIOS issue.
>>
>> Yakui, Did you actually check if the above was true?
> Yes. There is no definition of _PSS,_PCT,_PPC in DSDT table, which are
> required by acpi_cpufreq driver.At the same time there is no extra SSDT
> table.
It sounds like the BIOS just doesn't support frequency scaling.
Perhaps it's disabled in the BIOS setup. Or the system doesn't
support it at all.
If he can't find an option to enable it there he'll have to update it
and if there is no update he's out of luck.
I don't think Linux should be blamed for it.
>
>> >
>> > But it is very strange that cpufreq scaling can work on Windows XP.
>> > Will you please try the P4 clock cpufreq driver and see whether the
>> > scaling can work ? In fact P4 clock cpufreq driver is already replaced
>> > by acpi_cpufreq driver for the latest cpu.
>> > Anyway please try p4 clock cpufreq driver.
>>
>> What is the name of the driver? I'm not able to find any such driver
>> in Fedora 9 installed modules. There is only acpi-cpufreq and powernow-k8.
> The driver is P4-clockmod, which is located in the directory of
> arch/x86/kernel/cpu/cpufreq
Using p4 clockmod doesn't make sense because it doesn't really
safe any power and is often very slow.
-Andi
>>
next prev parent reply other threads:[~2008-08-11 10:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 10:00 cpufreq doesn't seem to work in Intel Q9300 S K
2008-08-03 10:31 ` none
2008-08-04 5:06 ` S K
2008-08-07 9:35 ` S K
2008-08-07 19:24 ` Alan Jenkins
2008-08-08 1:32 ` Zhao Yakui
2008-08-08 4:53 ` S K
2008-08-08 8:41 ` Alan Jenkins
2008-08-08 10:10 ` S K
2008-08-08 10:43 ` S K
2008-08-08 12:30 ` Thomas Renninger
2008-08-08 18:23 ` S K
2008-08-09 18:59 ` Thomas Renninger
2008-08-09 19:30 ` Thomas Renninger
2008-08-10 8:28 ` S K
2008-08-11 1:33 ` Zhao Yakui
2008-08-11 4:44 ` S K
2008-08-11 5:24 ` Zhao Yakui
2008-08-11 5:24 ` S K
2008-08-11 7:00 ` Alan Cox
2008-08-11 10:55 ` Andi Kleen [this message]
2008-08-11 13:15 ` S K
2008-08-11 13:23 ` Andi Kleen
2008-08-12 5:43 ` S K
2008-08-11 11:22 ` Arjan van de Ven
2008-08-11 11:38 ` Alexey Dobriyan
2008-08-11 11:53 ` Matthew Garrett
2008-08-11 14:02 ` Adrian Bunk
2008-08-11 14:07 ` Matthew Garrett
2008-08-11 14:12 ` Arjan van de Ven
2008-08-11 14:11 ` Arjan van de Ven
2008-08-11 16:03 ` Adrian Bunk
2008-08-11 16:20 ` Arjan van de Ven
2008-08-11 16:28 ` Adrian Bunk
2008-08-11 16:44 ` Arjan van de Ven
2008-08-12 19:27 ` Adrian Bunk
2008-08-11 19:33 ` Dominik Brodowski
2008-08-11 23:58 ` Arjan van de Ven
2008-08-12 19:03 ` Dominik Brodowski
2008-08-12 19:59 ` Arjan van de Ven
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=874p5r3jow.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nospamnoham@gmail.com \
--cc=trenn@suse.de \
--cc=yakui.zhao@intel.com \
/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