Re: loading new envstat properties reboots system

[Nicolas Joly <njoly%pasteur.fr@localhost>]

On Wed, Dec 15, 2010 at 05:14:31PM -0800, Paul Goyette wrote:
> On Thu, 16 Dec 2010, Nicolas Joly wrote:
> 
> >root@petaure [~]# envstat -S
> >root@petaure [~]# envstat
> >                 Current  CritMax  WarnMax  WarnMin  CritMin Unit
> >[amdtemp0]
> > CPU0 Sensor0:    51.250          -273.117                   degC
> > CPU0 Sensor1:    41.000          -273.117                   degC
> > CPU1 Sensor0:    51.500          -273.117                   degC
> > CPU1 Sensor1:    49.250          -273.117                   degC
> >
> >The -273.117 values looks ... wrong.
> 
> Definitely wrong.  :)  But most likely an error in amdtemp(4) driver.

Does not seems amdtemp related. I can reproduce it using swsensor.

njoly@lanfeust [~]# modstat -n swsensor
NAME             CLASS      SOURCE     REFS  SIZE     REQUIRES
root@lanfeust [~]# modload -i type=0 swsensor
root@lanfeust [~]# modstat -n swsensor
NAME             CLASS      SOURCE     REFS  SIZE     REQUIRES
swsensor         driver     filesys    0     1805     -

root@lanfeust [~]# envstat -d swsensor
          Current  CritMax  WarnMax  WarnMin  CritMin Unit
sensor:                                        
root@lanfeust [~]# cat swsensor.conf 
swsensor {
  sensor0 { critical-min = 85C; critical-max = 92C; }
}
root@lanfeust [~]# envstat -c swsensor.conf
root@lanfeust [~]# envstat -d swsensor     
          Current  CritMax  WarnMax  WarnMin  CritMin Unit
sensor:  92.000                     85.000     
root@lanfeust [~]# envstat -d swsensor
          Current  CritMax  WarnMax  WarnMin  CritMin Unit
sensor:         -273.117                       

Comparing `envstat -x' output from a freshly loaded sensor, and after
cleanup show that some limits remains :

root@lanfeust [NetBSD/envstat]# diff init.xml clean.xml 
3a4,5
>                         <key>critical-min</key>
>                         <integer>0</integer>
15a18,19
>                         <key>warning-max</key>
>                         <integer>32640</integer>

Hmm ... Where does the WarnMax limit comes from ? It should not
exists.

NB: envstat output looks bad when Temp value is 0uK, correct
otherwise.

NB2: What about adding ability to set an inital value when loading the
module; something like `modload -i type=0 -i value=273150000 swsensor' ?

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.