On Sat, Jan 29, 2011 at 12:31 PM, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
On Sat, 29 Jan 2011 12:18:31 -0800, Dylan wrote:
> On Sat, Jan 29, 2011 at 12:11 PM, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
> > Never use native hwmon drivers together with IPMI. They access the sameYou certainly do, as the w83627ehf driver (native hwmon driver) does
> > device in a non-synchronized manner, resulting in reads from / write to
> > the wrong register. The problem your describe is most certainly caused
> > by this. If your system uses IPMI, don't load native hwmon drivers.
>
> Thanks for your quick response. Your idea of conflicting reads/writes sounds
> very plausible.
> So, with UNRAID I am no explicitly loading any hwmon drives or IPMI drivers.
not load automatically. Most likely, you ran sensors-detect, and it
detected the chip and created a configuration file for you. As I am not
familiar with UNRAID, you'll have to figure out by yourself which
configuration file mentions the w83627ehf driver, and remove it. It's
certainly somewhere under /etc, so a brutal:
# grep -r w83627ehf /etc
might answer the question.
UnRAID is a pre-compiled kernel and filesystem that gets loaded into RAM each reboot. After digging through the .config provided I found it does indeed have w83627ehf compiled into the kernel.
I recompiled the kernel with the module not loaded by default and -- ta daa -- no more random alarms and warnings from my motherboard or the IPMI interface. But of course I also don't get any sensor data via lm-sensors.
As you are apparently using IPMI on this machine, the best solution is
> Can you give me a pointer as to how I might resolve this conflict?
to not load the w83627ehf driver. Which unfortunately means no
integration with libsensors-based monitoring applications, but IPMI
support comes at this price for the time being.
I did dig around to see if there was a ipmisensors module for my kernel but unfortunately there is not. It seems I'm left with ipmitool for now which is fine but I just don't get the nice lm-sensors integration I was hoping for. Ah well. Thank goodness there is no more alarms :)
> Is this an issue as how I've modified sensors3.conf or something moreThis is related to kernel modules, yes.
> fundamental with kernel modules?
--
Jean Delvare
Thanks again Jean. You helped me solve my problem.
Dylan Parker
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
