Re: Sporadic envstat(8)

[Sad Clouds <cryintothebluesky%googlemail.com@localhost>]

On Fri, 3 Dec 2010 11:33:21 +0000
Ian Clark <mrrooster%gmail.com@localhost> wrote:

> On 2 December 2010 13:53, Sad Clouds 
> <cryintothebluesky%googlemail.com@localhost> wrote:
> > On Thu, 2 Dec 2010 07:39:44 -0500
> > Michael <macallan%netbsd.org@localhost> wrote:
> >
> [snip]
> >
> > Which driver? I don't know, it doesn't say much. When sensors are working, 
> > running 'envstat -D' gives the following:
> >
> > coretemp0 (checking events every 30 seconds)
> > coretemp1 (checking events every 30 seconds)
> > coretemp2 (checking events every 30 seconds)
> > coretemp3 (checking events every 30 seconds)
> >
> > Your point about sensor taking a while to warm up is what I was thinking, 
> > however if that's the case, envsys framework should be intelligent enough 
> > to figure this out.
> >
> > My other thought was maybe the hardware was hiding the sensors, until the 
> > temperature was high enough that they were usable. Maybe envsys framework 
> > cannot cope with such dynamic actions? Who knows...
> >
> If you boot it cold (and get no temps reported), take a copy of the
> boot dmesg (from /var/run/dmesg.boot) then reboot with them working
> does a diff of the saved dmesg from the current one reveal anything?
> 
> Ian

Yeah I've done exactly what you suggested, there was no difference in dmesg.