From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Getting an alarm even with values between min/max
Date: Thu, 07 Aug 2008 07:31:28 +0000 [thread overview]
Message-ID: <489AA4D0.6010506@hhs.nl> (raw)
In-Reply-To: <489AA0CF.4010509@medizinische-genetik.de>
Marc Muehlfeld wrote:
> Hello.
>
> I run lm_sensors 2.6.5 on a Redhat 7.2 machine (it's a server for a legacy
> application).
>
> Nothing changed on the OS for ~3 years and I'm unsure, why I get an alarm
> since a few days on VCore1/VCore2 even the values are in the range:
>
> w83627hf-i2c-0-2c
> Adapter: SMBus AMD75x adapter at 80e0
> Algorithm: Non-I2C SMBus adapter
> #2 VCore1: +1.55 V (min = +1.44 V, max = +1.76 V) ALARM
> #2 VCore2: +1.60 V (min = +1.52 V, max = +1.68 V) ALARM
>
> What causes this?
>
Given that this setup has worked without alarms before, chances are pretty big
that those ALARMS are real, IOW the powersupply on your motherboard for the CPU
is starting to fail (bad elco's ?). An ALARM gets set when the voltage gets
outside the allowable window and then *stays set* even if the voltage returns
to normal. It gets cleared the first time you read it.
So I think the following is happening:
1) voltage briefly goes outside window, the w83627hf sets its alarm flag
2) you run sensors, voltage has returned to normal but the ALARM flag that was
set gets reported now (and normally also cleared)
You could try running sensors in quick succession, if this is an intermediate
failure, the ALARM should not be present on the second run. (But their might be
some bug causing it to stay set, thats some pretty old software you're running
there).
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2008-08-07 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 7:14 [lm-sensors] Getting an alarm even with values between min/max Marc Muehlfeld
2008-08-07 7:31 ` Hans de Goede [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=489AA4D0.6010506@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.