From: Wouter Verhelst <wouter@grep.be>
To: Ducrot Bruno <ducrot@poupinou.org>, cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sun, 11 Jan 2004 21:24:50 +0100 [thread overview]
Message-ID: <20040111202450.GB25048@grep.be> (raw)
In-Reply-To: <20040111200617.GA25713@dominikbrodowski.de>
On Sun, Jan 11, 2004 at 09:06:18PM +0100, Dominik Brodowski wrote:
> On Sun, Jan 11, 2004 at 08:56:19PM +0100, Wouter Verhelst wrote:
> > It mostly does, although I've had lockups when using the /proc interface
> > to switch CPU frequencies -- yes, should've reported that, but I only
> > now remember :)
>
> The /proc/ interface is deprecated,
Yes, I know. In fact, it being deprecated is the reason I started
playing with p4-clockmod in the first place :)
> and the acpi module is full of errors [I'm working on it, though...].
> You should use the /sys-fs interface with the acpi.ko module as well.
>
> > That does not change.
>
> Very strange... I'm out of ideas for the moment being.
I'm more and more convinced it's got something to do with cpufreqd. I
shut it down yesterday for about an hour, and nothing happened. Then I
restarted it, and -surprise- less than a minute later, the CPU was
throttled below the maximum speed.
--
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.
next prev parent reply other threads:[~2004-01-11 20:24 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
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 [this message]
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=20040111202450.GB25048@grep.be \
--to=wouter@grep.be \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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