Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 2003 15:51:51 -0500 (EST)
From:      Tuc <tuc@ttsg.com>
To:        kstewart@owt.com (Kent Stewart)
Cc:        freebsd-questions@freebsd.org
Subject:   Re: System instability (Revisited)
Message-ID:  <200303272051.h2RKppVY000237@himinbjorg.ttsg.com>
In-Reply-To: <200303270830.51025.kstewart@owt.com> from "Kent Stewart" at Mar 27, 2003 08:30:51 AM

next in thread | previous in thread | raw e-mail | index | archive | help
> > Since then, I reformatted, and installed 4.8-RC2 and rebuilt
> > everything from the ground up (Ports wise, NOT system).
> >
> > That was 2 weeks ago, and since then not 1 X lockup, no unknown core
> > files, and *1* reboot (Suprisingly less than 24 hours after starting
> > SETI@HOME).
> 
> I think you have hardware that is flaky. Seti uses 99+% of cpu and when 
> you start anything else that is major, it is rebooting.
>
	No, didn't say that, just wanted to let people know I ran for almost
2 weeks w/o a mishap, then less than 24 hours after SETI loaded, it dies *1*
time. Not since though.
>
> I would suspect 
> problems along the same lines as signal 11, i.e., heat or power 
> related.
> 
> I had a Celeron that would run for weeks but if I tried to build 
> XFree86-libraries and run Seti, it would reboot. Eventuially, the heat 
> got the cpu and the system completely died.
> 
	Its a laptop.... I just ran a whole bunch of DELL stuff, and it claims
everything is fine.... So how do I tell/prove its an issue?

		Thanks, Tuc/TTSG Internet Services, Inc.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303272051.h2RKppVY000237>