mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: clemens kurtenbach <moqua@kurtenba.ch>
To: linux-kernel@vger.kernel.org
Subject: cpufreq and p4 prescott
Date: Wed, 12 May 2004 17:28:38 +0200	[thread overview]
Message-ID: <40A242A6.4020002@kurtenba.ch> (raw)

Hi,

i have problems scaling down my p4 prescott 2.8 GHz.
In the /sys -tree all seems to be ok:

[ck@holodeck:cpufreq] pwd
/sys/devices/system/cpu/cpu0/cpufreq

[ck@holodeck:cpufreq] ls -1
cpuinfo_max_freq
cpuinfo_min_freq
scaling_available_frequencies
scaling_available_governors
scaling_driver
scaling_governor
scaling_max_freq
scaling_min_freq
scaling_setspeed

[ck@holodeck:cpufreq] cat *
2800000
350000
350000 700000 1050000 1400000 1750000 2100000 2450000 2800000
powersave userspace performance
p4-clockmod
userspace
2800000
350000
350000

[ck@holodeck:cpufreq] cat /proc/cpuinfo | grep Mhz
cpu MHz         : 2807.131
cpu MHz         : 2807.131

As you can see tools like cpudyn or powernowd successfully
change the entry in scaling_setspeed (also for cpu1),
but the real cpu clock stays at 2.8GHz ?

The cpudyn doc sais there's support for 'Intel Pentium 4, Intel Xeon'
CPU's, but is there support for p4 prescott ?

Has annyone here successfully scaled down a prescott ?

regards,
clee
-- 
moqua [at] gmx.net
moqua [at] kurtenba.ch

             reply	other threads:[~2004-05-12 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 15:28 clemens kurtenbach [this message]
2004-05-12 17:14 Dominik Brodowski
2004-05-13  9:19 ` clemens kurtenbach
2004-05-13 15:30   ` rutger
2004-05-13 12:06 ` Dominik Brodowski
2004-05-13 17:39 Dominik Brodowski
2004-05-14 21:47 ` rutger
2004-05-15  6:44   ` Dominik Brodowski
2004-05-15 10:52     ` rutger
2004-05-15 19:41       ` Dominik Brodowski
2004-05-16 13:20         ` Rutger Nijlunsing

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=40A242A6.4020002@kurtenba.ch \
    --to=moqua@kurtenba.ch \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®