mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark M. Hoffman" <mhoffman@lightlink.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: Re: [BK PATCH] i2c driver fixes for 2.6.2-rc2
Date: Thu, 29 Jan 2004 22:38:53 -0500	[thread overview]
Message-ID: <20040130033853.GG992@earth.solarsys.private> (raw)
In-Reply-To: <20040129225659.GA11872@werewolf.able.es>

* J.A. Magallon <jamagallon@able.es> [2004-01-29 23:56:59 +0100]:
> 
> On 2004.01.29, J.A. Magallon wrote:
> > 
> > werewolf:~# sensors
> > w83781d-isa-0290
> > Adapter: ISA adapter
> > VCore 1:   +1.97 V  (min =  +1.90 V, max =  +2.10 V)              
> > VCore 2:   +2.02 V  (min =  +1.90 V, max =  +2.10 V)              
> > +3.3V:     +3.23 V  (min =  +3.14 V, max =  +3.46 V)              
> > +5V:       +4.97 V  (min =  +4.73 V, max =  +5.24 V)              
> > +12V:     +12.04 V  (min = +11.37 V, max = +12.59 V)    
> 
> Oops, not so good:
>           
> > -12V:     -12.18 V  (min = -12.57 V, max = -11.35 V)       ALARM  
> > -5V:       -4.96 V  (min =  -5.25 V, max =  -4.74 V)       ALARM  
> 
> Why ALARM ?

The alarm indicator is "sticky".  Even though the present
readings are within limits, the alarm says that the voltage
moved outside its limit since the last time you ran sensors.

Trying running sensors 5 times, at 2 second intervals.  If
the voltage always stays within the limits but the alarm
is not cleared, then maybe there is a problem with the
driver.  If that's the case, please follow up on the sensors
mailing list.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com


  reply	other threads:[~2004-01-30  3:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 23:32 Greg KH
2004-01-27 23:34 ` [PATCH] " Greg KH
2004-01-27 23:34   ` Greg KH
2004-01-27 23:34     ` Greg KH
2004-01-27 23:34       ` Greg KH
2004-01-27 23:34         ` Greg KH
2004-01-27 23:34           ` Greg KH
2004-01-28 13:08             ` Typo (Re: [PATCH] i2c driver fixes for 2.6.2-rc2) David Martínez Moreno
2004-01-28 23:23               ` Greg KH
2004-01-29 11:27                 ` David Martínez Moreno
2004-01-29 19:47                   ` Greg KH
2004-01-30  9:58                     ` David Martínez Moreno
2004-01-31  0:55                       ` Greg KH
2004-01-29  0:44 ` [BK PATCH] i2c driver fixes for 2.6.2-rc2 J.A. Magallon
2004-01-29  0:47   ` J.A. Magallon
2004-01-29  8:44   ` Jean Delvare
2004-01-29 22:21     ` J.A. Magallon
2004-01-29 22:56       ` J.A. Magallon
2004-01-30  3:38         ` Mark M. Hoffman [this message]
2004-01-30  9:36           ` Jean Delvare
2004-01-30  9:18       ` Jean Delvare

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=20040130033853.GG992@earth.solarsys.private \
    --to=mhoffman@lightlink.com \
    --cc=jamagallon@able.es \
    --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

all inboxes | Powered by JetHome®