From owner-freebsd-questions@FreeBSD.ORG Thu Mar 27 12:51:55 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DC2337B401 for ; Thu, 27 Mar 2003 12:51:55 -0800 (PST) Received: from himinbjorg.ttsg.com (wallstreet34.kickstartusa.com [65.105.161.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F88F43FD7 for ; Thu, 27 Mar 2003 12:51:54 -0800 (PST) (envelope-from tuc@ttsg.com) Received: (from tuc@localhost) by himinbjorg.ttsg.com (8.12.8/8.12.8) id h2RKppVY000237; Thu, 27 Mar 2003 15:51:51 -0500 (EST) (envelope-from tuc) From: Tuc Message-Id: <200303272051.h2RKppVY000237@himinbjorg.ttsg.com> To: kstewart@owt.com (Kent Stewart) Date: Thu, 27 Mar 2003 15:51:51 -0500 (EST) In-Reply-To: <200303270830.51025.kstewart@owt.com> from "Kent Stewart" at Mar 27, 2003 08:30:51 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1 autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-questions@freebsd.org Subject: Re: System instability (Revisited) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2003 20:51:56 -0000 > > 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.