From: Jeremy Fitzhardinge <jeremy@goop.org>
To: tobias.bocanegra@day.com
Cc: cpufreq@lists.linux.org.uk, acpi-devel@kernel.org
Subject: Re: problems setting freq on dual core t2600, 2.6.17-1.2157_FC5smp
Date: Thu, 03 Aug 2006 16:01:23 -0700 [thread overview]
Message-ID: <44D28043.5010301@goop.org> (raw)
In-Reply-To: <8be731880608030605x6dbeb691kc7079a9d51fe87e9@mail.gmail.com>
Tobias Bocanegra wrote:
> hi,
> i don't know if this is the correct list to ask this question, if not
> just bash me :-)
>
> i have a intel dual core t2600 with 2.16ghz, running 2.6.17-1.2157_FC5smp
I've seen similar stuff on my T2400, expecially after resume. Check the
scaling_min/max_freq entries; I find that the cur is limited by their
contents.
I did a bit of debugging, and found the problem was that the acpi
functions on the policy change notifier change were vetoing the change,
because they though the max freq is 1GHz, rather than 1.83.
Unfortunately I don't have any of the logs at the moment; I was going to
do a more systematic examination of what's going on. But from a first
cut, it seems that something in ACPI is getting a more or less random
idea of what the current CPU max speed is.
BTW, this is a Thinkpad X60 with the most current BIOS installed (1.06?).
J
next prev parent reply other threads:[~2006-08-03 23:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 13:05 problems setting freq on dual core t2600, 2.6.17-1.2157_FC5smp Tobias Bocanegra
2006-08-03 15:33 ` Alexey Starikovskiy
2006-08-03 15:59 ` Tobias Bocanegra
2006-08-03 23:01 ` Jeremy Fitzhardinge [this message]
2006-08-05 17:42 ` Tobias Bocanegra
[not found] ` <44D59CC5.1010200@goop.org>
2006-08-06 9:09 ` Tobias Bocanegra
2006-08-06 9:32 ` Erik Slagter
2006-08-06 9:44 ` Tobias Bocanegra
2006-08-06 9:46 ` Erik Slagter
2006-08-06 10:02 ` Tobias Bocanegra
2006-08-06 10:18 ` Erik Slagter
2006-08-06 10:10 ` Tobias Bocanegra
2006-08-06 10:19 ` Erik Slagter
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 20:47 Pallipadi, Venkatesh
2006-08-04 8:46 ` Erik Slagter
2006-08-04 20:16 Pallipadi, Venkatesh
2006-08-04 20:43 ` Erik Slagter
2006-08-04 22:49 Pallipadi, Venkatesh
2006-08-06 14:10 Pallipadi, Venkatesh
2006-08-06 19:43 ` Tobias Bocanegra
2006-08-08 12:52 ` Thomas Renninger
2006-08-08 14:39 ` Tobias Bocanegra
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=44D28043.5010301@goop.org \
--to=jeremy@goop.org \
--cc=acpi-devel@kernel.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=tobias.bocanegra@day.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.