On Tue, Sep 10, 2002 at 04:52:33PM +0000, MLH wrote:
> On 10 Sep 2002 10:25:01 -0500, Frank van der Linden wrote:
> > On Mon, Sep 09, 2002 at 08:57:18PM +0000, MLH wrote:
> >> The only problems I have had with these are that the LM driver
> >> incorrectly calculates the cpu temperatures (port-i386/18205) and
> >> XF86 appears to be somewhat unstable. It appears to simply lock up
> >> the cpu it is running on - no core dump or anything. If XF86 locks
> >> up cpu1, cpu0 can still conveniently restart the machine, but if
> >> it is running on cpu0, the whole box appears to lock up. Is this
> >> consistent with known status?
> > 
> > It's actually the first time I've heard about such an XF86 problem
> > with the MP code. I'm running the MP code myself on my desktop
> > system (a dual Athlon, Tyan board), and am not seeing X problems.
> 
> For a while, I thought it was a heat-related failure, because the
> lm driver was indicating ~68C and ~72C cpu temperatures (the bios
> indicates more like ~45C) and it was behaving almost exactly like
> other athlons I have seen which were running too hot and under
> stress. X running xscreensaver or just resizing windows under some
> conditions seems to trigger it.

Just to verify, on the bios screen which presents the temperature, try
pressing return (or other keys which cause an update).  I've seen several
BIOSes which report bogus values until you do so.

-- 
Bill Squier (groo@old-ones.com)                          http://www.netbsd.org

        I know I don't deserve another chance, but this _is_ America,
        and as an American, aren't I entitled to one?  --Sideshow Bob.