Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765029AbZFLNvA (ORCPT ); Fri, 12 Jun 2009 09:51:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934138AbZFLNrr (ORCPT ); Fri, 12 Jun 2009 09:47:47 -0400 Received: from mx-out.daemonmail.net ([216.104.160.38]:48403 "EHLO mx-out.daemonmail.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934132AbZFLNrq (ORCPT ); Fri, 12 Jun 2009 09:47:46 -0400 From: "Michael S. Zick" Reply-To: lkml@morethan.org To: Harald Welte Subject: Re: [lm-sensors] [PATCH] hwmon: Add driver for VIA CPU core temperature Date: Fri, 12 Jun 2009 08:47:36 -0500 User-Agent: KMail/1.9.9 Cc: Jean Delvare , Tomaz Mertelj , Andrew Morton , linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org References: <20090609083406.GE25316@prithivi.gnumonks.org> <20090612125450.GK30843@prithivi.gnumonks.org> <200906120841.08114.lkml@morethan.org> In-Reply-To: <200906120841.08114.lkml@morethan.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906120847.46609.lkml@morethan.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2467 Lines: 56 On Fri June 12 2009, Michael S. Zick wrote: > On Fri June 12 2009, Harald Welte wrote: > > On Fri, Jun 12, 2009 at 06:46:45AM -0500, Michael S. Zick wrote: > > > > Temperature values are supposed to be expressed in millidegrees C, not > > > > degrees C as it seems to be doing (although 25 degrees C seems pretty > > > > low for a CPU temperature?) The drivers needs to multiply values by > > > > 1000 before exporting them to sysfs. Then "sensors" will report the > > > > correct temperature value. > > > > > > > > > > Ah, 25 degrees C is room temperature - real hard for the junction temperature > > > to be 25 degrees C with power applied; lacking an infinitely perfect heatsink. > > > > > > Look for an "off by one" error in shifting or masking the value. > > > > there is no shifting and the masking is 0xffffffff :) > > > > it might be that the BIOS is doing something wrong when programming the > > calibration MSR's at early botoup. I would need the contents of MSR > > 0x1160 ... 0x116C as well as 0x1152 and 0x1153 to be able to determine that. > > > > root@cb01:~# for r in 0x1160 0x1161 0x1162 0x1163 0x1164 0x1165 0x1166 0x1167 0x1168 0x1169 0x116a 0x116b 0x116c 0x1152 0x1153 ; do ./rdmsr $r ; done > MSR register 0x1160 => 08:04:98:10:b7:ef:8f:f4 > MSR register 0x1161 => 08:04:98:10:b7:fb:af:f4 > MSR register 0x1162 => 08:04:98:10:b7:ec:ff:f4 > MSR register 0x1163 => 08:04:98:10:b7:fa:cf:f4 > MSR register 0x1164 => 08:04:98:10:b7:f4:cf:f4 > MSR register 0x1165 => 08:04:98:10:b7:f3:2f:f4 > MSR register 0x1166 => 08:04:98:10:b7:f1:7f:f4 > MSR register 0x1167 => 08:04:98:10:b7:f2:0f:f4 > MSR register 0x1168 => 08:04:98:10:b7:ef:0f:f4 > MSR register 0x1169 => 08:04:98:10:b7:fc:8f:f4 > MSR register 0x116a => 08:04:98:10:b7:ef:8f:f4 > MSR register 0x116b => 08:04:98:10:b7:f8:bf:f4 > MSR register 0x116c => 08:04:98:10:b7:f9:df:f4 > MSR register 0x1152 => 08:04:98:10:b7:ed:5f:f4 > MSR register 0x1153 => 08:04:98:10:b7:ed:cf:f4 > > The high 32b look strange in that output - might be > the utility I used (attached). > > Mike > > Hmm ... if the utility is correct and I read that under a 16bit mask - that is 36,852 milliDegrees. Sounds about right for this machine and conditions. Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/