From: Jean Delvare <khali@linux-fr.org>
To: Ivanovich <ivanovich@menta.net>
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com,
"Nicolas Nilles" <nnilles@skycop.net>
Subject: Re: Kernel 2.6.0 and i2c-viapro posible Bug
Date: Sat, 10 Jan 2004 12:41:56 +0100 [thread overview]
Message-ID: <20040110124156.3b127c86.khali@linux-fr.org> (raw)
In-Reply-To: <200401091955.55007.ivanovich@menta.net>
> > I thinks that thgere is probably a bug in I2c-viapro module,
> > cuz when i load i2c-viapro after loading w82781d, my computer just
> > put very slow..., i try loading as modules in the kernel or built
> > in, in both cases i have the same problem.
>
> I have this very same board CUV4X_E and the same problem too (present
> in 2.6.0 and before)
> The workaround i found is to not initialize the chip "modprobe w83781d
> init=0"
>
> And answering some of your questions, yes, the slowdown is global, not
> only disk and it doesn't gets better if you unload the modules.
>
> It's fixed in 2.6.1? going to download+compile and see if it works.
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.
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.
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.
Thanks.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2004-01-10 11: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 [this message]
2004-01-10 14:40 ` Ivanovich
-- 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=20040110124156.3b127c86.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=ivanovich@menta.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nnilles@skycop.net \
--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