From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] w83793 related question
Date: Wed, 22 Apr 2009 20:57:03 +0000 [thread overview]
Message-ID: <20090422225703.790834da@hyperion.delvare> (raw)
In-Reply-To: <49E45712.6020906@aei.mpg.de>
On Wed, 22 Apr 2009 22:16:19 +0200, Rudolf Marek wrote:
> Hi,
>
> I have been thinking what it possibly could be. It seems like there might be two
> reasons:
>
> 1) the board is equipped with some kind of remote management conroller, which is
> also doing transactions on I2C
>
> Is there some?
>
> 2) the SMM mode is doing its own i2c transactions, interfering with the driver.
>
> The problem is that SMM iss transparent to OS.The only thing could possibly done
> is a BIOS change, or one could add some code to acquire global ACPI lock. It
> would require to modify the driver and add there those functions.
What makes you think there is a relation between SMM and ACPI?
>
> 3) Make a driver more bullet proof. Maybe it would be possible somehow to force
> the driver to have a longer timeouts, more retries etc.
This is pointless. If another entity is accessing the chip without
proper locking, no amount of timeouts or retries will help. In this
scenario, reported errors are in fact the best thing than can happen.
The worst case is silent misbehavior.
>
> I would still need to know how often this problem actually happens.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-04-22 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 9:27 [lm-sensors] w83793 related question Carsten Aulbert
2009-04-19 9:11 ` Rudolf Marek
2009-04-20 10:21 ` Carsten Aulbert
2009-04-20 19:41 ` Rudolf Marek
2009-04-20 19:44 ` Carsten Aulbert
2009-04-20 20:40 ` Carsten Aulbert
2009-04-22 20:16 ` Rudolf Marek
2009-04-22 20:27 ` Carsten Aulbert
2009-04-22 20:57 ` Jean Delvare [this message]
2009-04-23 6:57 ` Rudolf Marek
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=20090422225703.790834da@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.