From: Jean Delvare <khali@linux-fr.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1 regression: hwmon/w83627ehf: wrong fan speed
Date: Fri, 10 Aug 2007 23:08:31 +0200 [thread overview]
Message-ID: <20070810230831.59cbc50f@hyperion.delvare> (raw)
In-Reply-To: <46B6053E.2050708@s5r6.in-berlin.de>
Hi Stefan,
On Sun, 05 Aug 2007 19:13:34 +0200, Stefan Richter wrote:
> Mark M. Hoffman wrote:
> > Does this patch (against v2.6.23-rc2) fix it?
> >
> > commit f15c50e703c14ff7d72c3cb34e8e55417476a290
> > Author: Mark M. Hoffman <mhoffman@lightlink.com>
> > Date: Sun Aug 5 12:19:01 2007 -0400
> >
> > hwmon: read fan_div values during probe
> >
> > This patch forces the driver to read the fan divider values during early init.
> > Otherwise, a call to store_fan_min() could access uninitialized variables.
>
> Alas not; there is no change.
> (I applied on vanilla 2.6.23-rc2 and rebooted.)
I just tried 2.6.23-rc2 on a system where I use the w83627ehf hardware
monitoring driver, and was not able to reproduce the problem you
described. Fan speeds are reported properly for me. Which I kind of
expected, as I tested all my w83627ehf patches on this system before
submitting them.
Please try using sensors instead of ksensors, and confirm that the
behavior is the same. I'd like to rule out a problem in ksensors
itself. sensors will also report the fan divs, this is a useful
information given the problem you have.
Your original post suggests that the fan speed is supposed to change
depending on the system load? Or temperature? Please describe the
mechanism used to achieve this. Could it be that this mechanism isn't
working properly, and the reported (low) speeds are actually true?
What fan inputs are used by your CPU and system fans? "sensors
-c /dev/null" will tell.
Other than that, I can only ask for the same things Mark already
suggested: compile with HWMON debugging and provide the logs (this will
show what fan div the driver is trying to select), and try bisecting
using git to find out which patch exactly caused the problem.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2007-08-10 21:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 11:20 2.6.23-rc1 regression: hwmon/w83627ehf: wrong fan speed Stefan Richter
2007-08-05 11:28 ` Stefan Richter
2007-08-05 13:55 ` Mark M. Hoffman
2007-08-05 14:51 ` Stefan Richter
2007-08-05 15:17 ` Mark M. Hoffman
2007-08-05 16:21 ` Mark M. Hoffman
2007-08-05 17:13 ` Stefan Richter
2007-08-10 21:08 ` Jean Delvare [this message]
2007-08-10 22:29 ` Stefan Richter
2007-08-10 22:39 ` Stefan Richter
2007-08-11 2:30 ` [lm-sensors] " David Hubbard
2007-08-11 11:57 ` Jean Delvare
2007-08-11 15:41 ` Stefan Richter
2007-08-11 15:48 ` Stefan Richter
2007-08-12 9:21 ` Jean Delvare
2007-08-12 9:17 ` Jean Delvare
2007-08-12 10:34 ` Stefan Richter
2007-08-12 10:43 ` Stefan Richter
2007-08-12 17:49 ` Mark M. Hoffman
2007-08-12 16:06 ` 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=20070810230831.59cbc50f@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=stefanr@s5r6.in-berlin.de \
/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