Re: w83627ehf: Wrong values reported after resuming from suspend/hibernation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean,

Am 24.10.2012 20:05, schrieb Harald Judt:
[...]
Thank you for your patch. I've applied it on 3.6.2, and it seems to work
fine. The values are saved and restored correctly, and they also keep
changing after resume. Further it gave me a little insight in how
suspend/resume code works.

Sorry, I stand corrected. Not all min/max values have been restored:

Before suspend:
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.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:           +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM

After resume:
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.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:           +1.68 V  (min =  +0.00 V, max =  +0.00 V)  ALARM

I somehow missed the min/max differences in AVCC and +3.3V, too many numbers ;-)

But the rest is fine, double-checked now.

BTW: cpu0_vid is always +0.000 V, am I right assuming this simply isn't supported on my board?

Harald

--
`Experience is the best teacher.'


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


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux