From: Wouter Verhelst <wouter@grep.be>
To: cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sat, 10 Jan 2004 12:08:00 +0100 [thread overview]
Message-ID: <20040110110800.GA8294@grep.be> (raw)
In-Reply-To: <20040110101534.GA10003@dominikbrodowski.de>
[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]
On Sat, Jan 10, 2004 at 11:15:34AM +0100, Dominik Brodowski wrote:
> On Fri, Jan 09, 2004 at 07:18:51PM +0100, Wouter Verhelst wrote:
> > Hi,
> >
> > I can't seem to get my processor to run at full speed when using the
> > p4-clockmod driver:
> >
> > root@worldmusic:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor
> > userspace
> > root@worldmusic:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq
> > 2193205
> > root@worldmusic:/sys/devices/system/cpu/cpu0/cpufreq# echo 2193205 > scaling_setspeed
> > root@worldmusic:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_setspeed
> > 1925000
> >
> > What am I missing?
>
> Which kernel version are you using?
Vanilla 2.6.1, but I had the same problem with 2.6.0 (didn't try
p4-clockmod on any kernel before that).
> What does "dmesg" tell us?
234 lines of output. Seems a bit excessive to put that in this mail, so
I've put it on <http://users.pandora.be/wouter.verhelst/cpufreq.tgz>,
together with the contents of /proc/cpuinfo and my .config. If you need
any further information, please ask.
--
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
"Stop breathing down my neck." "My breathing is merely a simulation."
"So is my neck, stop it anyway!"
-- Voyager's EMH versus the Prometheus' EMH, stardate 51462.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-01-10 11:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08 ` Wouter Verhelst [this message]
2004-01-10 13:18 ` Dominik Brodowski
2004-01-10 15:02 ` Wouter Verhelst
2004-01-10 15:38 ` Dominik Brodowski
2004-01-10 16:30 ` Wouter Verhelst
2004-01-10 15:21 ` Wouter Verhelst
2004-01-10 15:41 ` Dominik Brodowski
2004-01-10 16:32 ` Wouter Verhelst
2004-01-10 18:53 ` Ducrot Bruno
2004-01-10 19:35 ` Wouter Verhelst
2004-01-11 15:48 ` Ducrot Bruno
2004-01-11 17:30 ` Dominik Brodowski
2004-01-11 18:05 ` Ducrot Bruno
2004-01-11 17:35 ` Dominik Brodowski
2004-01-11 19:56 ` Wouter Verhelst
2004-01-11 20:06 ` Dominik Brodowski
2004-01-11 20:24 ` Wouter Verhelst
2004-01-12 12:26 ` Ducrot Bruno
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=20040110110800.GA8294@grep.be \
--to=wouter@grep.be \
--cc=cpufreq@www.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 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.