On Wed, Jul 03, 2013 at 12:08:17PM -0400, Justin Piszcz wrote: > > > -----Original Message----- > From: Guenter Roeck [mailto:linux@xxxxxxxxxxxx] > Sent: Wednesday, July 03, 2013 10:42 AM > To: Justin Piszcz > Cc: linux-kernel@xxxxxxxxxxxxxxx; lm-sensors@xxxxxxxxxxxxxx > Subject: Re: 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) > Can you install superiotool and run "sudo superiotool -V -e" ? I would like to see raw data from the superio chip. > > 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 > You have to specify the raw attribute names, not the symbolic ones. You see the raw attribute names with "sensors -u". > $ 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 > Does the board have intrusion detection headers ? If so, you could close (bridge) the header(s) which should get rid of the alarm. Thanks, Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
