From: Ivanovich <ivanovich@menta.net>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: Kernel 2.6.0 and i2c-viapro posible Bug
Date: Sat, 10 Jan 2004 15:40:30 +0100 [thread overview]
Message-ID: <200401101540.30390.ivanovich@menta.net> (raw)
In-Reply-To: <20040110124156.3b127c86.khali@linux-fr.org>
On Dissabte 10 Gener 2004 12:41, Jean Delvare wrote:
> Could be fixed, because limits initialization has been removed from the
> w83781d driver. But since there is still some intialization stuff done,
> the problem may still be there. Please try and report. The "init=0"
> parameter is still there, so your workaround should still work.
Yes, seems fixed, slowdown no longer happens when loading the module in 2.6.1
But the via686a module doesn't get loaded when i "modprobe w83781d", just
i2c_sensor. No trace of any bus module in lsmod, not needed?
And the temperatures of sensors temp_input2 (micro) and temp_input3 (external
thermistor) seem to be halved. As reference, since i have no thermistor
attached, the number shown for/sys/bus/i2c/devices/1-002d/temp3 (div 100) in
2.6.0 was 255 now is 127. Board temp (temp_input1) seems to be right.
> If the problem is still present, I'd like you to do more tests. Edit the
> driver (drivers/i2c/chips/w83781d.c), look for the "w83781d_init_client"
> function. You'll find three blocks that are under a "init" conditional.
> I'd like you to disable each of them individually ("if (0) {" should do
> the trick) and see each time if the slowdown still occurs, so as to give
> us a hint on which command causes the slowdown.
Since it's working in 2.6.1 would it be of any use if I try this in 2.6.0 to
further isolate the problem?
> Also, at the moment a slowdown occurs and if you have ACPI support
> enabled, could you please check the throttling level (and the frequency,
> if that applies to your CPU)? I suspect that the motherboard is
> hardwired so as to enable throttling on overheat detection. A faulty
> init of the w83781d could trigger such an alarm and enable throttling,
> resulting in the slowdown you notice. Well, that's just a wild guess,
> but still worth verifying IMHO.
I think that's a good guess, I recall that with older versions of lm_sensors
in 2.4.xx just after loading the driver (without init=0), the pc speaker
would emit a very annoying high-pitch sound constantly, probably an overheat
alarm?
next prev parent reply other threads:[~2004-01-10 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:55 Kernel 2.6.0 and i2c-viapro posible Bug Ivanovich
2004-01-10 11:41 ` Jean Delvare
2004-01-10 14:40 ` Ivanovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 19:55 Nicolas Nilles
2004-01-07 21:30 ` Jean Delvare
2004-01-08 15:11 ` Nicolas Nilles
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=200401101540.30390.ivanovich@menta.net \
--to=ivanovich@menta.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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