On 08/23/2013 02:53 AM, Jean Delvare wrote:
On Fri, 23 Aug 2013 10:01:14 +0200, Jean Delvare wrote:
On Thu, 22 Aug 2013 09:13:36 -0700, Guenter Roeck wrote:
On Thu, Aug 22, 2013 at 06:09:01PM +0200, Toralf Förster wrote:
Why is that module not auto loaded ? Hhm ?
It never was. Maybe your relase update replaced /etc/modules.
Actually it was, since kernel v3.4 and commit 9b38096fd. And it works
Me surprised. Well, we live and learn. Guess that was due to introducing
MODULE_DEVICE_TABLE ?
for me with kernel v3.10, but no longer with kernel v3.11-rc6. In other
words I see the same regression Toralf is seeing. I have no explanation
for it at this point, but I have a few candidate commits for reversal.
I'll post again when I know more.
Reverting my 4 candidates did not help. We're up for a bisection I guess,
when I can find the time for it (i.e. not right now.)
I don't see a difference in the driver since 3.10 which would explain the problem.
If it is a generic problem, it would be surprising that no one else as seen
it with other modules.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
