severity 577822 important
retitle 577822 libsensors4 doesn't provide sensors.conf, cpufreqd should try to
initialize with sensors3.conf by default
thanks
On Thu, Apr 15, 2010 at 12:47:00AM +0200, Helmut Grohne wrote:
> On Thu, Apr 15, 2010 at 07:31:25AM +0900, Mattia Dongili wrote:
> > severity 577822 normal
>
> So damaging hardware is a normal bug... Maybe we should readjust all
> other bugs to wishlist.
you computer will turn off before that happens. If that is not the case
then there might be a bios (or sometimes kernel) problem.
Relying on userspace to perform this critical function is nonsense, but
your concern is understandable.
> > Would you mind describing what you're actually experiencing rather than
> > an ipotetical (and quite unlinkely) situation?
>
> I experience that without /etc/sensors.conf no rules (especially not the
> overheated rule) are matched, so cpufreqd does not change governors.
> This causes my cpu to overheat.
>
> > Also please, provide logs (running cpufreqd with -V7 generates a lot of
> > useful output to trak down issues).
>
> The interesting parts of those logs are:
> ...
> sensors_post_conf : no sensors.conf found, sensors disabled!
> ...
> plugin_handle_keyword : unandled keyword "sensor". Discarded
> parse_config_rule : WARNING! skipping config option "sensor"
> init_configuration : [Rule] name "overheated" has no options.
> Discarded.
> ...
> cpufreqd_loop : No Rule matches current system status.
> ...
yes. This is what I thought.
> > cpufreqd depends on libsensors4, have you considered using
> > /etc/sensors3.conf?
>
> I did, but cpufreqd does not let me configure that path.
have you tried this (from the manpage):
Section [sensors_plugin]
sensors_conf Define this directive to the sensors.conf file you
want cpufreqd to use to load the sensors library.
[sensors_plugin]
sensors_conf=/etc/sensors3.conf
[/sensors_plugin]
> > I guess a possible issue here is that cpufreqd _requires_ a sensors
> > config file while it's not really necessary to use one when initializing
> > the library..
>
> Correct. You can of course change cpufreqd, so it does not require this
> file.
this is the correct solution. I'll release a new version this weekend.
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
