From owner-freebsd-isp Mon Jul 3 10:45:31 2000 Delivered-To: freebsd-isp@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id BDA3B37C1F6 for ; Mon, 3 Jul 2000 10:45:26 -0700 (PDT) (envelope-from jim@siteplus.net) Received: from discover.siteplus.net (user-38lc8tb.dialup.mindspring.com [209.86.35.171]) by gull.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id KAA02645 for ; Mon, 3 Jul 2000 10:45:22 -0700 (PDT) Date: Mon, 3 Jul 2000 13:45:32 -0400 (EDT) From: Jim Weeks To: freebsd-isp@FreeBSD.ORG Subject: RE: Reading lmmon In-Reply-To: <3.0.5.32.20000703165217.0366ecd0@moat-gw.teksupport.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 3 Jul 2000, Rob Secombe wrote: > >: Motherboard Temp Voltages > >: > >: 255C / 491F / 528K Vcore1: +3.984V > >: Vcore2: +3.984V > >: Fan Speeds + 3.3V: +3.984V > >: + 5.0V: +6.654V > >: 1: 0 rpm +12.0V: +15.938V > >: 2: 0 rpm -12.0V: -15.938V > >: 3: 0 rpm - 5.0V: -6.654V > 255C Hmmm... all bits on in the byte maybe? and a fan speed of zero. This > looks more like a sensing problem to me. Could be a clock failure to the > A/D and fan counter. This is partially right. The problem with the reporting is that the bits are set. As to why I don't know. I am glad that I went to the machine to check this out though. CPU0's fan had given up the ghost. If the heat sink had not been large with a lot of fins no doubt the PII would have fried. Before cracking it open I put a probe right in the top of the case and recorded a temp of 148F which is above the shutdown limit of 140F. I am still surprised that everything else was functioning normally. I replaced the fan with one that did not have the monitor wire, the only one I could find on short notice, and rebooted into the BIOS setup. According to the data in the bios everything, with the exception of the CPU0 fan speed, is operating within acceptable limits. I would assume since the data is displayed correctly in the bios setup, clock failure should not be the problem. I still get the same data from "lmmon" and here is what I get from healthd. Jul 3 12:38:55 servername healthd: A value of 255.00 for Chip Set Temperature with a range of (0.00 <= n <= 30.00) Jul 3 12:38:55 servername healthd: A value of 0.00 for CPU #0 Temperature with a range of (10.00 <= n <= 30.00) Jul 3 12:38:55 servername healthd: A value of 0.00 for CPU #1 Temperature with a range of (10.00 <= n <= 30.00) Jul 3 12:38:55 servername healthd: A value of 0.00 for CPU #0 Cooling Fan with a range of (3000.00 <= n <= 9999.00) Jul 3 12:38:55 servername healthd: A value of 0.00 for CPU #1 Cooling Fan with a range of (3000.00 <= n <= 9999.00) Jul 3 12:38:55 servername healthd: A value of 0.00 for Case Fan Cooling Fan with a range of (3000.00 <= n <= 9999.00) Jul 3 12:38:55 servername healthd: A value of 4.08 for CPU #0 Core Voltage with a range of (1.95 <= n <= 2.05) Jul 3 12:38:55 servername healthd: A value of 4.08 for CPU #1 Core Voltage with a range of (1.95 <= n <= 2.05) Jul 3 12:38:55 servername healthd: A value of 4.08 for 3 Volt with a range of (2.50 <= n <= 3.50) Jul 3 12:38:55 servername healthd: A value of 6.85 for 5 Volt with a range of (4.50 <= n <= 5.40) Jul 3 12:38:55 servername healthd: A value of 15.50 for 12 Volt with a range of (11.00 <= n <= 13.00) Jul 3 12:38:55 servername healthd: A value of -14.16 for -12 Volt with a range of (-13.00 <= n <= -11.00) Jul 3 12:38:55 servername healthd: A value of -6.12 for -5 Volt with a range of (-5.50 <= n <= -4.50) Clearly not reporting corectly either. Any ideas as to why the reporting is not correct? Thanks, -- Jim Weeks -------- A mind is a terrible thing to lose! How I miss mine.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message