From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: bad temperature values from w83781d in 2.6.22
Date: Sun, 5 Aug 2007 12:26:04 +0200 [thread overview]
Message-ID: <20070805102604.GA9123@sommrey.de> (raw)
Hi,
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
+5 V: +4.81 V (min = +4.76 V, max = +5.24 V)
3 VSB: +3.30 V (min = +2.85 V, max = +3.15 V) ALARM
chs3 Fan: 2122 RPM (min = 2657 RPM, div = 4) ALARM
VRM2 Temp: -208°C (high = -176°C, hyst = -181°C) sensor = transistor
CPU1 Temp: +78.5°C (high = +80°C, hyst = +75°C) sensor = transistor ALARM
CPU2 Temp: +77.5°C (high = +80°C, hyst = +75°C) sensor = transistor ALARM
alarms:
beep_enable:
Sound alarm enabled
# cat /sys/bus/i2c/devices/0-002d/temp*_input
-209000
77500
77500
Any ideas?
-jo
--
-rw-r--r-- 1 jo users 62 2007-08-04 14:02 /home/jo/.signature
next reply other threads:[~2007-08-05 10:53 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 ` Joerg Sommrey [this message]
2007-08-05 11:20 ` bad temperature values from w83781d in 2.6.22 Rene Herman
2007-08-05 16:27 ` Joerg Sommrey
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=20070805102604.GA9123@sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
/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