From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: 'Guenter Roeck' <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard
Date: Wed, 03 Jul 2013 16:08:17 +0000 [thread overview]
Message-ID: <007101ce7807$88cfb160$9a6f1420$@lucidpixels.com> (raw)
In-Reply-To: <20130703144201.GA10323@roeck-us.net>
-----Original Message-----
From: Guenter Roeck [mailto:linux@roeck-us.net]
Sent: Wednesday, July 03, 2013 10:42 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
[ .. ]
This is surprising and might be where the alarm comes from. What output do
you
get if you load the coretemp driver ?
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +38.0 C (high = +81.0 C, crit = +91.0 C)
Core 0: +36.0 C (high = +81.0 C, crit = +91.0 C)
Core 1: +35.0 C (high = +81.0 C, crit = +91.0 C)
Core 2: +35.0 C (high = +81.0 C, crit = +91.0 C)
Core 3: +34.0 C (high = +81.0 C, crit = +91.0 C)
Core 4: +37.0 C (high = +81.0 C, crit = +91.0 C)
Core 5: +38.0 C (high = +81.0 C, crit = +91.0 C)
> PCH_CHIP_TEMP: +0.0 C
> PCH_CPU_TEMP: +0.0 C
> PCH_MCH_TEMP: +0.0 C
> intrusion0: ALARM
> intrusion1: ALARM
Are those not connected ?
The intrusion headers are not connected, also, I have not dug into it but
when you try to ignore the PECI or those PCH* lm_sensors seems to ignore the
rule.
sensors3.conf:
ignore PCH_CHIP_TEMP
ignore PCH_CPU_TEMP
ignore PCH_MCH_TEMP
$ sensors |tail -n 4
PCH_CHIP_TEMP: +0.0 C
PCH_CPU_TEMP: +0.0 C
PCH_MCH_TEMP: +0.0 C
Ignoring intrusion works though:
ignore intrusion0
ignore intrusion1
nct6776-isa-0a30
Adapter: ISA adapter
Vcore: +0.84 V (min = +0.54 V, max = +1.49 V)
in1: +1.84 V (min = +1.62 V, max = +1.99 V)
AVCC: +3.28 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.28 V (min = +2.98 V, max = +3.63 V)
in4: +1.50 V (min = +1.35 V, max = +1.65 V)
in5: +1.26 V (min = +1.13 V, max = +1.38 V)
in6: +1.06 V (min = +0.92 V, max = +1.34 V)
3VSB: +3.57 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.47 V (min = +2.70 V, max = +3.63 V)
fan1: 1007 RPM (min = 700 RPM)
fan2: 1317 RPM (min = 700 RPM)
fan3: 1102 RPM (min = 700 RPM)
fan4: 1059 RPM (min = 700 RPM)
fan5: 998 RPM (min = 700 RPM)
SYSTIN: +40.0 C (high = +75.0 C, hyst = +70.0 C) sensor thermistor
CPUTIN: +31.5 C (high = +95.0 C, hyst = +92.0 C) ALARM sensor thermistor
AUXTIN: +23.0 C (high = +80.0 C, hyst = +75.0 C) sensor thermistor
PECI Agent 0: +0.0 C (high = +95.0 C, hyst = +92.0 C)
(crit = +100.0 C)
PCH_CHIP_TEMP: +0.0 C
PCH_CPU_TEMP: +0.0 C
PCH_MCH_TEMP: +0.0 C
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Guenter Roeck'" <linux@roeck-us.net>
Cc: <linux-kernel@vger.kernel.org>, <lm-sensors@lm-sensors.org>
Subject: RE: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard
Date: Wed, 3 Jul 2013 12:08:17 -0400 [thread overview]
Message-ID: <007101ce7807$88cfb160$9a6f1420$@lucidpixels.com> (raw)
In-Reply-To: <20130703144201.GA10323@roeck-us.net>
-----Original Message-----
From: Guenter Roeck [mailto:linux@roeck-us.net]
Sent: Wednesday, July 03, 2013 10:42 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
[ .. ]
This is surprising and might be where the alarm comes from. What output do
you
get if you load the coretemp driver ?
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +38.0 C (high = +81.0 C, crit = +91.0 C)
Core 0: +36.0 C (high = +81.0 C, crit = +91.0 C)
Core 1: +35.0 C (high = +81.0 C, crit = +91.0 C)
Core 2: +35.0 C (high = +81.0 C, crit = +91.0 C)
Core 3: +34.0 C (high = +81.0 C, crit = +91.0 C)
Core 4: +37.0 C (high = +81.0 C, crit = +91.0 C)
Core 5: +38.0 C (high = +81.0 C, crit = +91.0 C)
> PCH_CHIP_TEMP: +0.0 C
> PCH_CPU_TEMP: +0.0 C
> PCH_MCH_TEMP: +0.0 C
> intrusion0: ALARM
> intrusion1: ALARM
Are those not connected ?
The intrusion headers are not connected, also, I have not dug into it but
when you try to ignore the PECI or those PCH* lm_sensors seems to ignore the
rule.
sensors3.conf:
ignore PCH_CHIP_TEMP
ignore PCH_CPU_TEMP
ignore PCH_MCH_TEMP
$ sensors |tail -n 4
PCH_CHIP_TEMP: +0.0 C
PCH_CPU_TEMP: +0.0 C
PCH_MCH_TEMP: +0.0 C
Ignoring intrusion works though:
ignore intrusion0
ignore intrusion1
nct6776-isa-0a30
Adapter: ISA adapter
Vcore: +0.84 V (min = +0.54 V, max = +1.49 V)
in1: +1.84 V (min = +1.62 V, max = +1.99 V)
AVCC: +3.28 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.28 V (min = +2.98 V, max = +3.63 V)
in4: +1.50 V (min = +1.35 V, max = +1.65 V)
in5: +1.26 V (min = +1.13 V, max = +1.38 V)
in6: +1.06 V (min = +0.92 V, max = +1.34 V)
3VSB: +3.57 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.47 V (min = +2.70 V, max = +3.63 V)
fan1: 1007 RPM (min = 700 RPM)
fan2: 1317 RPM (min = 700 RPM)
fan3: 1102 RPM (min = 700 RPM)
fan4: 1059 RPM (min = 700 RPM)
fan5: 998 RPM (min = 700 RPM)
SYSTIN: +40.0 C (high = +75.0 C, hyst = +70.0 C) sensor =
thermistor
CPUTIN: +31.5 C (high = +95.0 C, hyst = +92.0 C) ALARM sensor =
thermistor
AUXTIN: +23.0 C (high = +80.0 C, hyst = +75.0 C) sensor =
thermistor
PECI Agent 0: +0.0 C (high = +95.0 C, hyst = +92.0 C)
(crit = +100.0 C)
PCH_CHIP_TEMP: +0.0 C
PCH_CPU_TEMP: +0.0 C
PCH_MCH_TEMP: +0.0 C
Thanks,
Guenter
next prev parent reply other threads:[~2013-07-03 16:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 12:35 [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard Justin Piszcz
2013-07-03 12:35 ` Justin Piszcz
2013-07-03 14:42 ` [lm-sensors] " Guenter Roeck
2013-07-03 14:42 ` Guenter Roeck
2013-07-03 16:08 ` Justin Piszcz [this message]
2013-07-03 16:08 ` Justin Piszcz
2013-07-03 16:33 ` Guenter Roeck
2013-07-03 16:33 ` Guenter Roeck
2013-07-03 16:47 ` Justin Piszcz
2013-07-03 16:47 ` Justin Piszcz
2013-07-03 17:17 ` Guenter Roeck
2013-07-03 17:17 ` Guenter Roeck
2013-07-03 17:21 ` Justin Piszcz
2013-07-03 17:21 ` Justin Piszcz
2013-07-03 20:56 ` Guenter Roeck
2013-07-03 20:56 ` Guenter Roeck
2013-07-11 8:47 ` Jean Delvare
2013-07-11 8:47 ` Jean Delvare
2013-07-11 13:57 ` Justin Piszcz
2013-07-11 13:57 ` Justin Piszcz
2013-07-03 20:59 ` Justin Piszcz
2013-07-03 21:00 ` Justin Piszcz
2013-07-03 21:00 ` Justin Piszcz
2013-07-03 22:28 ` Guenter Roeck
2013-07-03 22:28 ` Guenter Roeck
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='007101ce7807$88cfb160$9a6f1420$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.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.