From: Paul Crawford <psc@sat.dundee.ac.uk>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Module load order dependency
Date: Sat, 01 Jun 2013 10:27:25 +0000 [thread overview]
Message-ID: <51A9CC8D.2010105@sat.dundee.ac.uk> (raw)
I encountered a problem using the lm-sensors package along with the
fancontrol package where the various drivers for the temperature sensing
chips would be loaded in differing orders at boot time.
This leads to the abstracted paths of, for example,
'/sys/class/hwmon/hwmon0' and '/sys/class/hwmon/hwmon1' changing places
and the fancontrol package doing nothing as it believes the hardware is
different or misconfigured.
This is also a risk for the Linux watchdog daemon that could be using
such a path for temperature sensing (I added the capability recently to
use lm-sensors outputs), leading to a far more irksome problem than
simply full-speed fans!
Is this enumeration something that lm-sensors performs, or is it a
kernel issue? As this appears to be quite important for actually using
the capabilities, what can be done to fix it?
I added my crude solution (to make sure all of the modules are in
/etc/modules, and not some auto-loaded and others explicitly added) to
the bug report here:
https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/576602
Regards, Paul
--
Dr. Paul S. Crawford
c/o Satellite Station
University of Dundee
Small's Wynd, Dundee, DD1 4HN
Email: psc@sat.dundee.ac.uk
Tel: +44 (0)1382 38 4687
The University of Dundee is a Scottish Registered Charity, No. SC015096
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2013-06-01 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 10:27 Paul Crawford [this message]
2013-06-02 11:03 ` [lm-sensors] Module load order dependency Jean Delvare
2013-06-02 11:20 ` Jean Delvare
2013-06-03 13:43 ` Paul Crawford
2013-06-03 14:19 ` Jean Delvare
2013-06-03 15:01 ` Paul Crawford
2013-06-04 11:28 ` Jean Delvare
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=51A9CC8D.2010105@sat.dundee.ac.uk \
--to=psc@sat.dundee.ac.uk \
--cc=lm-sensors@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 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.