From: Joerg Sommrey <jo@sommrey.de>
To: Rene Herman <rene.herman@gmail.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: bad temperature values from w83781d in 2.6.22
Date: Sun, 5 Aug 2007 18:27:47 +0200 [thread overview]
Message-ID: <20070805162747.GA30184@sommrey.de> (raw)
In-Reply-To: <46B5B277.8060402@gmail.com>
Thanks for your reply.
the sensors.conf I'm currently using is provided by Tyan, so this seems
to be ok. One major difference that I can see: I don't have compute
statements for the CPU temperatures. If I use your config, I get 7.8°C
:-)
So there is definitely some difference in our hardware environment. OTOH
with the "right" compute statement the problem seems fixable.
BTW: there is another hwmon chip on the board, a w83627hf. Up to 2.6.21
this was managed by the w83781d driver, too. Now I use the w83627hf
driver (on the isa bus). No problem with that part.
-jo
On Sun, Aug 05, 2007 at 01:20:23PM +0200, Rene Herman wrote:
> On 08/05/2007 12:26 PM, Joerg Sommrey wrote:
>
> >after upgrading from 2.6.21 to 2.6.22 the CPU temperatures shown by
> >w83781d look unreal. They were in a range from 40°C when idle to
> >75°C under full load with 2.6.21. The values shown now are in a very
> >small range from 77°C to 82°C. From the (low) noise of the fan I can
> >tell that the temperature is <50°C.
> >The third temperature shown is completely wrong.
> >
> >I have a Tyan Tiger MPX board with a w83782d chip. Output from
> >"sensors":
> >
> >w83782d-i2c-0-2d
> >Adapter: SMBus AMD768 adapter at 80e0
>
> As a datapoint, the same W83782D on AMD756 (also I2C) works correctly with
> 2.6.22:
>
> w83782d-i2c-0-2d
> Adapter: SMBus AMD756 adapter at 50e0
>
> Jean Delvare recently worked on the ISA interface to these chips but it
> seems this would not be the cause if you are also using I2C. Our hardware
> appears rather identical...
>
> I've attached (an excerpt of) my /etc/sensors.conf -- I once dug through
> the datasheets for those compute lines for example so perhaps its still
> useful even if 2.6.21 working for you probably means you don't have a
> config problem.
>
> Rene.
>
next prev parent reply other threads:[~2007-08-05 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070805183219.0d54802b.akpm@linux-foundation.org>
2007-08-05 10:26 ` bad temperature values from w83781d in 2.6.22 Joerg Sommrey
2007-08-05 11:20 ` Rene Herman
2007-08-05 16:27 ` Joerg Sommrey [this message]
2007-08-08 1:03 ` Mark M. Hoffman
2007-08-08 15:17 ` Joerg Sommrey
2007-08-09 3:56 ` [lm-sensors] " Mark M. Hoffman
2007-08-09 7:09 ` Joerg Sommrey
2007-08-09 12:26 ` [PATCH] " Mark M. Hoffman
2007-08-09 16:41 ` Joerg Sommrey
2007-08-12 18:18 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070805162747.GA30184@sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox