From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Dave Jones <davej@redhat.com>,
cpufreq@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: Is e_powersaver safe to auto-load?
Date: Wed, 22 Feb 2012 01:13:39 +0000 [thread overview]
Message-ID: <4F444143.6000505@interia.pl> (raw)
In-Reply-To: <1329003190.325.78.camel@deadeye>
> The e_powersaver driver comes with a dire warning in Kconfig help:
>
> VIA C7 Enhanced PowerSaver (DANGEROUS)
>
> This adds the CPUFreq driver for VIA C7 processors. However, this driver
> does not have any safeguards to prevent operating the CPU out of spec
> and is thus considered dangerous. Please use the regular ACPI cpufreq
> driver, enabled by CONFIG_X86_ACPI_CPUFREQ.
>
> Following the bug report<http://bugs.debian.org/566208>, Debian's
> cpufrequtils init script was changed to stop loading it. The driver was
> later disabled in Debian kernel configurations. Rafał appears to have
> made it somewhat safer since then, but the help text has not been
> changed.
>
> Since commit fa8031aefec0cf7ea6c2387c93610d99d9659aa2 ('cpufreq: Add
> support for x86 cpuinfo auto loading v4') the driver will be auto-loaded
> on some systems. If it is still dangerous then it should surely not be
> auto-loaded. But if it is now believed to be safe then the help text
> should be updated to say so.
>
> Ben.
>
Hello again,
Mainboard in question is VIA Epia SN10000EG rev. A1. I have access to it
now. I've tested it briefly for a couple of hours and it seems to work fine with
3.2 kernel. I will let you know if more extensive testing will give different result.
Rafał
eps: Detected VIA Model A C7
eps: Current voltage = 1004mV
eps: Current multiplier = 10
eps: Highest voltage = 1004mV
eps: Highest multiplier = 10
eps: Lowest voltage = 956mV
eps: Lowest multiplier = 8
eps: ACPI limit 1.0GHz
prev parent reply other threads:[~2012-02-22 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 23:33 Is e_powersaver safe to auto-load? Ben Hutchings
2012-02-12 12:30 ` Rafał Bilski
2012-02-22 1:13 ` Rafał Bilski [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=4F444143.6000505@interia.pl \
--to=rafalbilski@interia.pl \
--cc=ak@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.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 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.