From: "Mattia Dongili" <malattia@linux.it>
To: Marco Cusmai <cusmai@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: speedstep-ich issue
Date: Mon, 2 Oct 2006 10:21:42 +0200 (CEST) [thread overview]
Message-ID: <38599.85.47.20.193.1159777302.squirrel@picard.linux.it> (raw)
In-Reply-To: <66f5c650610020114v22cc56f9i5dbee03349ade1d0@mail.gmail.com>
On Mon, October 2, 2006 10:14 am, Marco Cusmai said:
> On 10/2/06, Dominik Brodowski <linux at dominikbrodowski.net> wrote:
>>
>> Hi,
>>
>> On Fri, Sep 29, 2006 at 09:49:42PM +0000, Marco cusmai wrote:
>> > cat scaling_available_frequencies : 1130500 731500
>> > cat scaling_min_freq : 731500
>> > cat scaling_max_freq : 731500
>>
>> Yes, then it won't scale any more -- the CPU will only be set to a value
>> between scaling_min_freq and scaling_max_freq. Therefore, please check
>> the
>> configuration file for cpufreqd (or any other cpufreq daemon you're
>> running).
>>
>> Thanks,
>> Dominik
>>
> For my tests I've already disabled the cpufreqd deamon at startup.. The
> results are the same.
> I've also tried the following:
>
> echo 1130500 > scaling_setspeed
> cat scaling_cur_freq : 731500
try this before:
$ echo 1130500 > scaling_max_freq
As explained, scaling_max_freq and scaling_min_freq define the upper and
lower limit to which the processor is bound (this is a software enforced
limit), so if this limit is MAX=MIN=731500 then the kernel won't allow
1130500.
--
mattia
:wq!
prev parent reply other threads:[~2006-10-02 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 11:11 speedstep-ich issue Marco cusmai
2006-09-29 17:40 ` Mattia Dongili
2006-09-29 21:49 ` Marco cusmai
2006-10-02 2:13 ` Dominik Brodowski
2006-10-02 8:14 ` Marco Cusmai
2006-10-02 8:21 ` Mattia Dongili [this message]
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=38599.85.47.20.193.1159777302.squirrel@picard.linux.it \
--to=malattia@linux.it \
--cc=cpufreq@lists.linux.org.uk \
--cc=cusmai@gmail.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