From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 25 12:19:41 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66DA216A417 for ; Fri, 25 Jan 2008 12:19:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 631F413C447 for ; Fri, 25 Jan 2008 12:19:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2A85F1CC031; Fri, 25 Jan 2008 04:19:41 -0800 (PST) Date: Fri, 25 Jan 2008 04:19:41 -0800 From: Jeremy Chadwick To: Attila Nagy Message-ID: <20080125121941.GA33060@eos.sc1.parodius.com> References: <4799B997.6080404@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4799B997.6080404@fsn.hu> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: Fetching thermal information from HP servers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 12:19:41 -0000 On Fri, Jan 25, 2008 at 11:27:35AM +0100, Attila Nagy wrote: > Any ideas what could be done to make the hardware sensors usable on HP > servers? I have a bunch of DL3xx, BL2xp, BL4xxc machines running FreeBSD > and all of them have: > hw.acpi.thermal.tz0.temperature: 8.3C > hw.acpi.thermal.tz0._PSV: 9.8C > hw.acpi.thermal.tz0._CRT: 31.3C > > These values are constant on all machines, regardless of the number of > CPUs, the type and the load. The sysctls remaining static is due to the BIOS vendor choosing to make them static values, rather than tying them into the HWM hardware on the board. This is common on a lot of Asus consumer motherboards as well. All you can do is complain to the system/BIOS manufacturer. It ultimately depends on what HWM is on all of the above servers, and whether or not utilities like sysutils/mbmon or sysutils/healthd (the code between the two is very similar, with sysutils/mbmon being more recent) can talk to the IC via old ISA I/O ports or via SMBus drivers. This also depends on some BIOS code to be in place. I'm in a similar boat with our Supermicro SuperServer 5015M-T+ boxes, which use a Winbond W83627EHF IC for serial/lpt/floppy/etc. as well as providing HWM capability. I've been hacking on some code to talk to it for a while via SMBus, and am having some mixed results. (I'm probably going to have to talk to Supermicro...) If HWM is important to you enough to switch OSes, take a look at Linux's lm-sensors framework (which is now in the 2.4 and 2.6 kernels), as it's significantly more advanced than the above two. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |