All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] w83627ehf: Wrong values reported after resuming from suspend/hibernation
Date: Mon, 22 Oct 2012 21:40:00 +0000	[thread overview]
Message-ID: <20121022214000.GA15343@roeck-us.net> (raw)
In-Reply-To: <50856051.5070803@gmx.at>

On Mon, Oct 22, 2012 at 05:03:45PM +0200, Harald Judt wrote:
> Hi,
> 
> After resuming from suspend or hibernation, the Vbat value is
> reported to be 0.0. Before that, it reported the correct value.
> Min/max values are wrong too.
> 
> Linux-3.6.2, ASRock Z77 Extreme4 BIOS v1.80.
> 
> Before suspend:
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore:         +0.97 V  (min =  +0.00 V, max =  +1.74 V)
> in1:           +1.84 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> AVCC:          +3.34 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:         +3.34 V  (min =  +2.98 V, max =  +3.63 V)
> in4:           +1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in5:           +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 3VSB:          +3.47 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:          +3.31 V  (min =  +2.70 V, max =  +3.63 V)
> fan1:            0 RPM  (min =    0 RPM)  ALARM
> fan2:         1289 RPM  (min =    0 RPM)  ALARM
> fan3:          724 RPM  (min =    0 RPM)  ALARM
> fan4:          661 RPM  (min =    0 RPM)  ALARM
> fan5:         1076 RPM  (min =    0 RPM)  ALARM
> SYSTIN:        +37.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM
> sensor = thermistor
> CPUTIN:        +28.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
> thermistor
> AUXTIN:        +33.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
> thermistor
> PECI Agent 0:  +32.0°C
> cpu0_vid:     +0.000 V
> intrusion0:   ALARM
> intrusion1:   ALARM
> 
> After resuming:
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore:         +0.97 V  (min =  +0.00 V, max =  +1.74 V)
> in1:           +1.84 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> AVCC:          +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> +3.3V:         +3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in4:           +1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in5:           +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 3VSB:          +3.47 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> Vbat:          +0.00 V  (min =  +0.00 V, max =  +0.00 V)
> fan1:            0 RPM  (min =    0 RPM)  ALARM
> fan2:         1271 RPM  (min =    0 RPM)  ALARM
> fan3:          734 RPM  (min =    0 RPM)  ALARM
> fan4:          673 RPM  (min =    0 RPM)  ALARM
> fan5:         1093 RPM  (min =    0 RPM)  ALARM
> SYSTIN:        +36.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM
> sensor = thermistor
> CPUTIN:        +26.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
> thermistor
> AUXTIN:        +33.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
> thermistor
> PECI Agent 0:  +30.0°C
> cpu0_vid:     +0.000 V
> intrusion0:   ALARM
> intrusion1:   ALARM
> 
> Reloading the module helps. Of course, a fresh boot too ;-)
> 
The driver doesn't implement suspend/resume support, so it is not very
surprising that the limits get lost - and it looks like vbat monitoring
is disabled by default, so that gets lost as well.

Someone would have to submit a patch to add suspend/resume support to
the driver ... any takers out there ?

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2012-10-22 21:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 15:03 [lm-sensors] w83627ehf: Wrong values reported after resuming from suspend/hibernation Harald Judt
2012-10-22 21:40 ` Guenter Roeck [this message]
2012-10-23  7:14 ` Jean Delvare
2012-10-23  9:57 ` Harald Judt
2012-10-23 11:45 ` Jean Delvare
2012-10-23 12:08 ` Harald Judt
2012-10-23 12:34 ` Jean Delvare
2012-10-23 14:01 ` Guenter Roeck
2012-10-23 16:32 ` Jean Delvare
2012-10-23 19:02 ` Harald Judt
2012-10-24  3:45 ` Guenter Roeck
2012-10-24  8:39 ` Jean Delvare
2012-10-24 18:05 ` Harald Judt
2012-10-24 18:14 ` Harald Judt
2012-10-24 19:23 ` Jean Delvare
2012-10-25  9:53 ` Guenter Roeck
2012-10-25 17:26 ` Harald Judt
2012-10-25 19:07 ` Jean Delvare
2012-10-25 19:16 ` Harald Judt
2012-10-25 20:37 ` Guenter Roeck
2012-10-25 23:49 ` Guenter Roeck
2012-10-26  0:41 ` Guenter Roeck
2012-10-26  0:55 ` Harald Judt
2012-10-26  7:27 ` Jean Delvare
2012-10-26 14:06 ` Guenter Roeck
2012-10-26 14:15 ` Jean Delvare
2013-07-28 20:43 ` Harald Judt
2013-07-28 21:43 ` Guenter Roeck
2013-07-28 22:28 ` Guenter Roeck
2013-07-29  2:24 ` Harald Judt
2013-07-29  2:47 ` Harald Judt
2013-07-29  6:58 ` Guenter Roeck
2013-07-29  9:12 ` Harald Judt
2013-07-29 15:27 ` Harald Judt
2013-07-29 22:46 ` Guenter Roeck
2013-07-31 22:11 ` Guenter Roeck
2013-08-01  9:08 ` Harald Judt
2013-08-01 13:42 ` Guenter Roeck
2013-08-01 14:36 ` Harald Judt
2013-08-01 17:46 ` Guenter Roeck

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=20121022214000.GA15343@roeck-us.net \
    --to=linux@roeck-us.net \
    --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.