From owner-freebsd-questions@FreeBSD.ORG Thu Mar 27 11:12:57 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 8E92637B48C for ; Thu, 27 Mar 2003 11:12:57 -0800 (PST) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E0F443FCB for ; Thu, 27 Mar 2003 11:12:56 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([129.44.43.88]) by out001.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030327191255.FUVW29952.out001.verizon.net@mac.com> for ; Thu, 27 Mar 2003 13:12:55 -0600 Message-ID: <3E834D1E.3050500@mac.com> Date: Thu, 27 Mar 2003 14:12:30 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd Questions References: <20030327132506.B60255-100000@malkav.snowmoon.com> In-Reply-To: <20030327132506.B60255-100000@malkav.snowmoon.com> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [129.44.43.88] at Thu, 27 Mar 2003 13:12:55 -0600 X-Spam-Status: No, hits=-27.9 required=5.0 tests=AWL,IN_REP_TO,QUOTED_EMAIL_TEXT,RCVD_IN_UNCONFIRMED_DSBL, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: kernel panics, lots of them 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 19:12:59 -0000 jaime@snowmoon.com wrote: [ ... ] >> There is memtest and cpuburn in the ports; try running those and see >> whether you can get the system to crash. > > Just to verify before I run these programs in the middle of the > work day: The purpose of these programs is to try to crash the system, > right? :) You should be prepared for the system to crash, yes. :-) Of course, the point of these tests is that your hardware _should_ be able to run them for days or weeks without any problems with system stability. But if the system cooling/memory timing/etc is marginal, these will probably cause the system to panic within a few hours, which helps confirm where the problem lies... -Chuck