From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Supermicro X7SPA-HF: in4 ALARM
Date: Fri, 06 Apr 2012 20:24:57 +0000 [thread overview]
Message-ID: <021401cd1433$56049180$020db480$@lucidpixels.com> (raw)
In-Reply-To: <01fa01cd1430$fed0b990$fc722cb0$@lucidpixels.com>
-----Original Message-----
From: Jean Delvare [mailto:khali@linux-fr.org]
Sent: Friday, April 06, 2012 4:19 PM
To: Justin Piszcz
Cc: lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] Supermicro X7SPA-HF: in4 ALARM
On Fri, 6 Apr 2012 16:08:12 -0400, Justin Piszcz wrote:
> Hello,
>
> Was curious why the max voltage does not show up properly for in4 (VDIMM)
> for this X7SPA-HF using lm sensors 3.3.1 or 3.3.2?
>
> On the sensor reading page for IPMI:
> VDIMM Normal 1.84 Volts
You should not mix IPMI with native Linux hardware monitoring driver.
There is no mutual exclusion on device access, and havoc can (and will)
happen.
Ah, good to know!
> ignore intrusion0
Did you run "sensors -s" after changing the configuration file?
Whoops, missed this, thanks, that was it-- if the board's built-in IPMI monitoring (accessible via IPMI web interface) is going to interfere with lm_sensors, its probably best not to use it and just refer to the IPMI via the web interface?
Justin.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-04-06 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 20:08 [lm-sensors] Supermicro X7SPA-HF: in4 ALARM Justin Piszcz
2012-04-06 20:14 ` Justin Piszcz
2012-04-06 20:19 ` Jean Delvare
2012-04-06 20:24 ` Justin Piszcz [this message]
2012-04-06 20:56 ` Jean Delvare
2012-05-13 22:30 ` Ben Kamen
2012-05-13 23:57 ` Ben Kamen
2012-05-14 0:53 ` Guenter Roeck
2012-05-14 5:42 ` 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='021401cd1433$56049180$020db480$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--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.