NetBSD Problem Report #43543

From  Tue Jun 29 17:08:49 2010
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id 4F95463BA66
	for <>; Tue, 29 Jun 2010 17:08:49 +0000 (UTC)
Message-Id: <>
Date: Tue, 29 Jun 2010 19:08:43 +0200 (CEST)
Subject: ipmi(4) driver fails to collect Fan2 signal on Intel X38ML board
X-Send-Pr-Version: 3.95

>Number:         43543
>Category:       kern
>Synopsis:       ipmi(4) driver fails to collect Fan2 signal on Intel X38ML board
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 29 17:10:00 +0000 2010
>Last-Modified:  Fri Jul 30 09:55:01 +0000 2010
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 5.0.2
Dr. Nagler & Company GmbH


System: NetBSD 5.0.2 (INSTALL) #2: Tue May 18 18:00:44 CEST 2010 wgstuken@s012:/export/NetBSD-5.0.2/N+C-build/.OBJDIR_amd64/export/NetBSD-5.0.2/src/sys/arch/amd64/compile/INSTALL amd64
Architecture: x86_64
Machine: amd64
	After booting the system reports soon that FAN-2 rotation speed is critical low.
	envstat(8) reports 0 RPM.

	But that is simply not true. The fan is working and I've switch FAN-3 and FAN-2 hardware but the
	problem stays at FAN-2.
	When booting 4.0, a value other than 0 RPM is reported by envstat on the same board.
	So the problem is not at the hardware. For unknown reasons the ipmi-driver fails to collect
	the correct value for the FAN speed for FAN-2 on all of our boards in 5.0.2 while 4.0 reports
	some values.

	Here the complete output of envstat(8) on the 5.0.2 system:

                       Current  CritMax  CritMin  CritCap     Unit
  cpu0 temperature:     40.000                                degC
  cpu1 temperature:     40.000                                degC
   P1 Therm Margin:    199.000                                degC
     Chassis Fan 3:       9906                                 RPM
     Chassis Fan 2:          0                                 RPM
     Chassis Fan 1:      11934                                 RPM
   BB Ambient Temp:     23.000                                degC
     Processor Vcc:      1.274                                   V
          BB +5.0V:      5.085                                   V
     BB +3.3V STBY:      3.255                                   V
          BB +3.3V:      3.286                                   V
       BB +1.8V SM:      1.793                                   V

	(remark: the value for P1 Term Margin look bad too, but the value reported under 4.0 is the same.
	The value for BB Ambient Temp looks good here - was bad (e.g. -105) in 4.0 - see below.)

	The output of "envstat -r" on a 4.0 system with the same HW:

P1 Therm Margin:    198.000 degC
BB Ambient Temp:   -106.000 degC
  Chassis Fan 3:      11934 RPM
  Chassis Fan 2:       6942 RPM
  Chassis Fan 1:       4914 RPM
  Processor Vcc:      1.274 V
       BB +5.0V:      5.061 V
  BB +3.3V STBY:      3.223 V
       BB +3.3V:      3.286 V
    BB +1.8V SM:      1.803 V

	(remark: the large difference in RPM between all FAN's is suspect in 4.0 too, but the values changes
	over time, so it looks at least like "real" values from some sensors ...)

	boot any 5.0.2 kernel ipmi configured on an X38ML board - it will fail to collect the RPM value
	for FAN2 on an X38ML board. Tested on more than on board where 4.0 reports a (correct) value.
	not know up to now - sorry - no time to do additional debugging at the moment.
	If I can add some additional information without a lot of work, I will do it. Please ask for it.

From: Michael van Elst <>
Subject: Re: kern/43543 ipmi(4) driver fails to collect Fan2 signal on
 Intel X38ML board
Date: Fri, 30 Jul 2010 11:52:34 +0200

 The ipmi driver only knows about linear sensor values (in fact, it
 ignores the linearization function). My system (HP ML110G4) returns
 something like 1/(val * 10^-7 + offset) which always results in 0
 because the code doesn't handle fractions and ignores the 1/X step.

 ipmi on the 4.0 system does the same, but the envstat output
 is probably not generated from ipmi.

                                 Michael van Elst
                                 "A potential Snark may lurk in every tree."


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.