From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] after some days,
Date: Thu, 20 May 2010 12:03:15 +0000 [thread overview]
Message-ID: <20100520140315.7f01813c@hyperion.delvare> (raw)
In-Reply-To: <g2p8cb75a4a1005110155u5b359f97z8e16ab5a2c475455@mail.gmail.com>
Hi Arne,
Please don't top-post.
> 2010/5/12 Jean Delvare <khali@linux-fr.org>:
> > On Tue, 11 May 2010 11:39:33 +0200, Jean Delvare wrote:
> > I took a look, I see the BIOS is defining an I/O region as part of
> > PNP0C02 for the hardware monitoring chip (you probably can see it
> > in /proc/ioports), but it doesn't seem to make any use of it. So I
> > would rule out a BIOS interaction.
On Mon, 17 May 2010 10:01:41 +0200, Arne Riecken wrote:
> What to do now to track down the problem? I need to check the sensors
> data. But doing sensors -s in a cron job is no real solution.
We still have to determine whether the driver is responsible for the
issue or not. If you can't live without the driver being loaded, we
would have to either add an option to turn the driver to read-only
mode, or to log all writes so that you can check what happens exactly.
In both cases, this requires rebuilding the driver. Are you willing and
able to do this? If you are, let me know and I'll provide a patch.
Honestly, I suspect a hardware defect. Nobody else ever reported a
similar problem, while this driver is very popular.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-05-20 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 8:55 [lm-sensors] after some days, Arne Riecken
2010-05-11 9:39 ` Jean Delvare
2010-05-11 10:57 ` Arne Riecken
2010-05-12 7:33 ` Jean Delvare
2010-05-17 8:01 ` Arne Riecken
2010-05-20 12:03 ` Jean Delvare [this message]
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=20100520140315.7f01813c@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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 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.