From: Thomas Renninger <trenn@suse.de>
To: cpufreq@lists.linux.org.uk
Subject: Re: Core 2 Duo E8400 stepping 6 not recognised
Date: Thu, 17 Jul 2008 14:44:25 +0200 [thread overview]
Message-ID: <200807171444.26396.trenn@suse.de> (raw)
In-Reply-To: <20080717001145.122c97b7.ldarby@tuffmail.com>
Hi,
sorry this is a bit unrelated...
On Thursday 17 July 2008 01:11:45 Laurence Darby wrote:
> Hi,
>
> I booted linux 2.6.26 with cpufreq.debug=3, and it gives the following:
>
> [ 0.391292] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> [ 0.391623] ACPI: ACPI0007:00 is registered as cooling_device0
> [ 0.391623] ACPI: Processor [CPU0] (supports 8 throttling states)
> [ 0.391623] cpufreq-core: CPU 1: _PPC is 0 - frequency not limited
> [ 0.391292] ACPI: ACPI0007:01 is registered as cooling_device1
> [ 0.391292] ACPI: Processor [CPU1] (supports 8 throttling states)
Wow, _PPC is evaluated before cpufreq is activated even the initial _PPC call
got removed some time ago.
This could be related to the ThinkPads get stuck on lowest freq problem.
Ingo Molnar already sent something similar, but did not fully ensure that _PPC
is only called after cpufreq has been initialized:
git commit e4233dec749a3519069d9390561b5636a75c7579
I send something to the related bug...
> [ 8.228001] acpi-cpufreq: acpi_cpufreq_init
> [ 8.228001] acpi-cpufreq: acpi_cpufreq_early_init
_PPC should not be called before these...
Thomas
next prev parent reply other threads:[~2008-07-17 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 23:11 Core 2 Duo E8400 stepping 6 not recognised Laurence Darby
2008-07-17 12:44 ` Thomas Renninger [this message]
2008-07-18 12:50 ` Laurence Darby
2008-07-20 0:12 ` Laurence Darby
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=200807171444.26396.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@lists.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