linux-kernel - Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro X9SRL-F motherboard

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Jul 2013 09:33:11 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
 X9SRL-F motherboard

On Wed, Jul 03, 2013 at 12:08:17PM -0400, Justin Piszcz wrote:
> 
> 
> -----Original Message-----
> From: Guenter Roeck [mailto:linux@...ck-us.net] 
> Sent: Wednesday, July 03, 2013 10:42 AM
> To: Justin Piszcz
> Cc: linux-kernel@...r.kernel.org; lm-sensors@...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)
> 
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/