From: Joerg Sommrey <jo@sommrey.de>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] bad temperature values from w83781d in 2.6.22
Date: Thu, 09 Aug 2007 07:09:15 +0000 [thread overview]
Message-ID: <20070809070915.GA24252@sommrey.de> (raw)
In-Reply-To: <20070809035642.GE3584@jupiter.solarsys.private>
Hi Mark,
On Wed, Aug 08, 2007 at 11:56:42PM -0400, Mark M. Hoffman wrote:
> Hi Joerg:
>
> * Joerg Sommrey <jo@sommrey.de> [2007-08-08 17:17:16 +0200]:
> > Hi Mark,
> >
> > just to eliminate as many impacts as possible, I did:
> > - reinstall the unmodified sensors.conf from Tyan's support page
> > - power off before rebooting
> >
> > A call to "sensors -s" is done without errors in all cases.
> > The module parameters I use currently with both kernels:
> >
> > options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49
> > options w83627hf force_addr=0x0c00
> >
> > When I first realized the problem, I didn't use w83627hf yet. Results
> > are the same when w83781d is used as driver for w83627hf.
> > Parameters in that case just from Tyan:
> >
> > options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49 force_w83627hf=0,0x2c force_subclients=0,0x2c,0x4a,0x4b init=0
> >
> > "My" i2cdump doesn't accept an -y option, maybe a Debianism. Results
> > see below.
>
> Newer i2cdump skips the 5-second warning when given -y, that's all.
>
> > ### 2.6.21 ###############################
> > Script started on Wed Aug 8 16:53:10 2007
> > bear:~/hwmon# i2cdump 0 0x2d b 0 0x4e
>
> (snip tons of results)
>
> 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.
>
> 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.
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.
-jo
--
-rw-r--r-- 1 jo users 62 2007-08-08 21:06 /home/jo/.signature
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Sommrey <jo@sommrey.de>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] bad temperature values from w83781d in 2.6.22
Date: Thu, 9 Aug 2007 09:09:15 +0200 [thread overview]
Message-ID: <20070809070915.GA24252@sommrey.de> (raw)
In-Reply-To: <20070809035642.GE3584@jupiter.solarsys.private>
Hi Mark,
On Wed, Aug 08, 2007 at 11:56:42PM -0400, Mark M. Hoffman wrote:
> Hi Joerg:
>
> * Joerg Sommrey <jo@sommrey.de> [2007-08-08 17:17:16 +0200]:
> > Hi Mark,
> >
> > just to eliminate as many impacts as possible, I did:
> > - reinstall the unmodified sensors.conf from Tyan's support page
> > - power off before rebooting
> >
> > A call to "sensors -s" is done without errors in all cases.
> > The module parameters I use currently with both kernels:
> >
> > options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49
> > options w83627hf force_addr=0x0c00
> >
> > When I first realized the problem, I didn't use w83627hf yet. Results
> > are the same when w83781d is used as driver for w83627hf.
> > Parameters in that case just from Tyan:
> >
> > options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49 force_w83627hf=0,0x2c force_subclients=0,0x2c,0x4a,0x4b init=0
> >
> > "My" i2cdump doesn't accept an -y option, maybe a Debianism. Results
> > see below.
>
> Newer i2cdump skips the 5-second warning when given -y, that's all.
>
> > ### 2.6.21 ###############################
> > Script started on Wed Aug 8 16:53:10 2007
> > bear:~/hwmon# i2cdump 0 0x2d b 0 0x4e
>
> (snip tons of results)
>
> 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.
>
> 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.
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.
-jo
--
-rw-r--r-- 1 jo users 62 2007-08-08 21:06 /home/jo/.signature
next prev parent reply other threads:[~2007-08-09 7:09 UTC|newest]
Thread overview: 17+ 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
2007-08-08 1:03 ` [lm-sensors] " Mark M. Hoffman
2007-08-08 1:03 ` Mark M. Hoffman
2007-08-08 15:17 ` [lm-sensors] " Joerg Sommrey
2007-08-08 15:17 ` Joerg Sommrey
2007-08-09 3:56 ` [lm-sensors] " Mark M. Hoffman
2007-08-09 3:56 ` Mark M. Hoffman
2007-08-09 7:09 ` Joerg Sommrey [this message]
2007-08-09 7:09 ` Joerg Sommrey
2007-08-09 12:26 ` [lm-sensors] [PATCH] " Mark M. Hoffman
2007-08-09 12:26 ` Mark M. Hoffman
2007-08-09 16:41 ` [lm-sensors] [PATCH] bad temperature values from w83781d in Joerg Sommrey
2007-08-09 16:41 ` [PATCH] bad temperature values from w83781d in 2.6.22 Joerg Sommrey
2007-08-12 18:18 ` [lm-sensors] [PATCH] bad temperature values from w83781d in Jean Delvare
2007-08-12 18:18 ` [PATCH] bad temperature values from w83781d in 2.6.22 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=20070809070915.GA24252@sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.