All of lore.kernel.org
 help / color / mirror / Atom feed
From: ch@westend.com (Christian Hammers)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [Ticket #2078] sensor values are sometimes wrong
Date: Mon, 24 Oct 2005 10:11:58 +0000	[thread overview]
Message-ID: <20051024081121.GB10262@westend.com> (raw)
In-Reply-To: <20051021083606.GB19748@westend.com>

Hello

On Sun, Oct 23, 2005 at 10:40:38PM +0200, Rudolf Marek wrote:
> > My problem is that sensors sometimes reports confusing values i.e.
> > - it prints ALERT although the corresponding values are fine, the ALERT
> >   then vanished in the next read
> > - sensor values give suddenly 0 or arbitrary values
> > - configured limits are 0 for one or two reads and then go back to the
> >   defined value
> 
> This sounds like there might be something else accessing the chip. Did
> you check log if there are no i2c bus related problems?
There are no related syslog messages and I'm not aware of any other
application using the i2c bus. There's no TV card in this server, are
there other likely candidates?

> We may also implement some checks to asb100 read routine to be sure
> that the reads actualy succeed instead of failing silencely.

bye,

-christian-

-- 
Christian Hammers             WESTEND GmbH  |  Internet-Business-Provider
Technik                       CISCO Systems Partner - Authorized Reseller
                              L?tticher Stra?e 10      Tel 0241/701333-11
ch@westend.com                D-52064 Aachen              Fax 0241/911879


  parent reply	other threads:[~2005-10-24 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 10:37 [lm-sensors] [Ticket #2078] sensor values are sometimes wrong Christian Hammers
2005-10-21 11:39 ` Grant Coady
2005-10-21 12:07 ` Christian Hammers
2005-10-23 22:40 ` Rudolf Marek
2005-10-24 10:11 ` Christian Hammers [this message]
2005-10-25 22:49 ` 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=20051024081121.GB10262@westend.com \
    --to=ch@westend.com \
    --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.