From: Thomas Renninger <trenn@suse.de>
To: Rainer Maier <RaMaier@gmx.de>
Cc: cpufreq@vger.kernel.org
Subject: Re: Fehler bei cpufreq-info
Date: Tue, 02 Apr 2013 10:42:30 +0200 [thread overview]
Message-ID: <3485704.XfQbseOPt4@skinner.arch.suse.de> (raw)
In-Reply-To: <51558EDC.2040503@gmx.de>
Hi,
On Friday, March 29, 2013 01:53:48 PM Rainer Maier wrote:
> cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
cpufrequtils is outdated.
Please use cpupower which is the successor.
> Bitte melden Sie Fehler an cpufreq@vger.kernel.org.
> analysiere CPU 0:
> Treiber: p4-clockmod
P4-clockmod is evil and does not save much/any power.
If you have trouble with it (lagging applications/performance), best
blacklist p4-clockmod driver.
Thomas
next prev parent reply other threads:[~2013-04-02 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 12:53 Fehler bei cpufreq-info Rainer Maier
2013-03-29 13:47 ` Viresh Kumar
2013-04-02 8:42 ` Thomas Renninger [this message]
2013-04-02 21:29 ` Rainer Maier
2013-04-03 7:53 ` Petr Šabata
2013-04-05 14:01 ` Thomas Renninger
2013-04-05 14:31 ` Petr Šabata
2013-04-05 15:04 ` Thomas Renninger
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=3485704.XfQbseOPt4@skinner.arch.suse.de \
--to=trenn@suse.de \
--cc=RaMaier@gmx.de \
--cc=cpufreq@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