From: "Mark M. Hoffman" <mhoffman@lightlink.com>
To: Joerg Sommrey <jo@sommrey.de>,
LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: [PATCH] bad temperature values from w83781d in 2.6.22
Date: Thu, 9 Aug 2007 08:26:19 -0400 [thread overview]
Message-ID: <20070809122619.GF3584@jupiter.solarsys.private> (raw)
In-Reply-To: <20070809070915.GA24252@sommrey.de>
Hi Joerg:
> On Wed, Aug 08, 2007 at 11:56:42PM -0400, Mark M. Hoffman wrote:
> > Thanks for sending all that. I see one bug clearly, and I'm pretty close to
> > seeing the other one. But for tonight, I need sleep.
There's just one bug after all. The second was a figment of my sleep-deprived
imagination.
> > In the meantime, please try this command as root, against the newer kernel,
> > *after* you've done 'sensors -s':
> >
> > # i2cset -f 0 0x2d 0x5d 0x0e b
> >
> > Wait > 2 seconds for the hardware to update itself, then run 'sensors' again.
> > I'm pretty sure you'll see the correct temps.
* Joerg Sommrey <jo@sommrey.de> [2007-08-09 09:09:15 +0200]:
> The displayed temperatures changed to 67.5°C / 66.0°C. Still, this seems to
> be too high. The power supply's fan runs too slow for such CPU
> temperatures. In older kernels it becomes noisy above 50°C.
>
> Under load the temperatures shown are around 95°C, way too high.
My bad, there's a second i2cset command that would have done it. Please try
this patch against v2.6.22.
* * * * *
commit a3333f720da3a173153b00cebc129c48cd3a40af
Author: Mark M. Hoffman <mhoffman@lightlink.com>
Date: Thu Aug 9 08:12:46 2007 -0400
hwmon: fix w83781d temp sensor type setting
Commit 348753379a7704087603dad403603e825422fd9a introduced a regression that
caused temp2 and temp3 sensor type settings to be written to temp1 instead.
The result is that temp sensor readings could be way off.
Signed-off-by: Mark M. Hoffman <mhoffman@lightlink.com>
diff --git a/drivers/hwmon/w83781d.c b/drivers/hwmon/w83781d.c
index f85b48f..c95909c 100644
--- a/drivers/hwmon/w83781d.c
+++ b/drivers/hwmon/w83781d.c
@@ -740,9 +740,9 @@ store_sensor(struct device *dev, struct device_attribute *da,
static SENSOR_DEVICE_ATTR(temp1_type, S_IRUGO | S_IWUSR,
show_sensor, store_sensor, 0);
static SENSOR_DEVICE_ATTR(temp2_type, S_IRUGO | S_IWUSR,
- show_sensor, store_sensor, 0);
+ show_sensor, store_sensor, 1);
static SENSOR_DEVICE_ATTR(temp3_type, S_IRUGO | S_IWUSR,
- show_sensor, store_sensor, 0);
+ show_sensor, store_sensor, 2);
/* I2C devices get this name attribute automatically, but for ISA devices
we must create it by ourselves. */
--
Mark M. Hoffman
mhoffman@lightlink.com
next prev parent reply other threads:[~2007-08-09 12:34 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
2007-08-05 11:20 ` 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 ` Mark M. Hoffman [this message]
2007-08-09 16:41 ` [PATCH] " 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=20070809122619.GF3584@jupiter.solarsys.private \
--to=mhoffman@lightlink.com \
--cc=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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
all inboxes | Powered by JetHome®