From: Thomas Renninger <trenn@suse.de>
To: "S K" <nospamnoham@gmail.com>
Cc: "Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
"Zhao Yakui" <yakui.zhao@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Sat, 9 Aug 2008 20:59:47 +0200 [thread overview]
Message-ID: <200808092059.47863.trenn@suse.de> (raw)
In-Reply-To: <aff5deaf0808081123s1fbe6a5cn7847e9cb053c1f5a@mail.gmail.com>
On Friday 08 August 2008 08:23:25 pm S K wrote:
> > Try updating the BIOS.
> > I expect your CPU is too new and the BIOS cannot export the correct freq
> > values for the specific CPU yet.
> >
> > Thomas
>
> The BIOS is already at the latest version :( Is the above comment the
> only possible reason for the issue?
It is very likely.
I did not go through the DSDT table(s) myself, but if this is true:
> According to the online ACPI spec, the BIOS should expose _PCT, _PSS and PPC
> objects if it supports multiple CPU performance states (aka P-states,
> cpufreq). I ran your acpidump.txt through acpixtract to generate the DSDT,
> and decompiled it using iasl. It did not contain any of _PCT, _PSS and
> _PPC.
your BIOS does not export basic CPU freq data. The only way to get cpufreq
working on latest Intel HW is through ACPI and acpi-cpufreq driver.
It may happen that above functions are somewhat hidden in SSDT tables but
loading and finding the CPU freq functions generally works quite well.
Mark Langsdorf reported some acpi breakage in .27-rc1, this could also be the
reason.
That a BIOS update is needed for latest CPUs is common. I expect your machine
is rather new?
There also is a cpufreq list which moved recently, the latest one you should
post to is this one:
cpufreq@vger.kernel.org
Thomas
next prev parent reply other threads:[~2008-08-09 18:43 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 [this message]
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
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=200808092059.47863.trenn@suse.de \
--to=trenn@suse.de \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nospamnoham@gmail.com \
--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