From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Problem with order of module loading
Date: Wed, 04 Feb 2009 10:05:36 +0000 [thread overview]
Message-ID: <20090204110536.2ddaa6a4@hyperion.delvare> (raw)
In-Reply-To: <20090125021151.GE16739@paradise.net.nz>
Volker,
On Fri, 30 Jan 2009 17:23:36 +0100, Jean Delvare wrote:
> On Wed, 28 Jan 2009 09:06:28 +0100, Jean Delvare wrote:
> > I have discussed this a bit with Kay Sievers yesterday. He suggested
> > that we can use the modalias files in sysfs together with "modprobe -n"
> > to find out whether a loaded hwmon driver has been auto-loaded or not.
> > This would let us exclude kernel modules from /etc/sysconfig/lm_sensors
> > based on whether they auto-load rather than based on whether they were
> > loaded when sensors-detect was run. This should be way more robust than
> > my initial proposal, to a point where I think it would make sense to
> > give it a try.
>
> Damn, it isn't as easy as I thought. Not all drivers follow the Linux
> device driver model to the letter. Actually, most hwmon drivers do not,
> because they create their own devices. Once such a driver is loaded, it
> appears to be autoloading (its devices have modalias strings that point
> to the driver) but in fact it is not. This fools my new code into
> thinking that pretty much all loaded hwmon drivers were autoloaded.
>
> Thus I fear I will have to limit the scope of my autoloading detection
> code to PCI devices. At least this covers the k8temp driver, which is
> probably the one that causes the more trouble in practice.
I have finally committed a change which should address your issue:
http://www.lm-sensors.org/changeset/5635
Basically, PCI and USB drivers which are auto-loaded on a given system
are no longer listed in /etc/sysconfig/lm_sensors. That way,
"rclm_sensors restart" will not unload and reload drivers which are
already present at boot time. This is the best approach from a
performance point of view, and it is also stable across reconfiguration
(running sensors-detect twice doesn't change the outcome.)
Please give a try to:
http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect
and confirm that it solves your problem (k8temp should no longer be
listed, so the hwmon class device numbers should stay stable across
reboots.)
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2009-02-04 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 2:11 [lm-sensors] Problem with order of module loading Volker Kuhlmann
2009-01-25 10:00 ` Jean Delvare
2009-01-25 11:08 ` Volker Kuhlmann
2009-01-25 13:47 ` Jean Delvare
2009-01-26 9:47 ` Volker Kuhlmann
2009-01-26 14:57 ` Jean Delvare
2009-01-27 8:27 ` Jean Delvare
2009-01-28 8:06 ` Jean Delvare
2009-01-30 16:23 ` Jean Delvare
2009-02-04 10:05 ` Jean Delvare [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=20090204110536.2ddaa6a4@hyperion.delvare \
--to=khali@linux-fr.org \
--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.