From owner-freebsd-questions@FreeBSD.ORG Sun Nov 6 21:20:33 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 1C93416A41F for ; Sun, 6 Nov 2005 21:20:33 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: from smtpout1.ywave.com (ycomradius.yelmtel.com [216.227.100.60]) by mx1.FreeBSD.org (Postfix) with SMTP id BD54943D46 for ; Sun, 6 Nov 2005 21:20:32 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: (qmail 25299 invoked by uid 502); 6 Nov 2005 21:20:31 -0000 Received: from dsl28217.ywave.com (HELO ?192.168.1.65?) (micahjon@ywave.com@216.227.115.217) by 0 with SMTP; 6 Nov 2005 21:20:31 -0000 X-CLIENT-IP: 216.227.115.217 X-CLIENT-HOST: dsl28217.ywave.com Message-ID: <436E739E.8020605@ywave.com> Date: Sun, 06 Nov 2005 13:20:30 -0800 From: Micah User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freeBSD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Diagnosing reboot under load X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Nov 2005 21:20:33 -0000 My desktop system just started doing this last night. I was upgrading Gnome using the handy shell script they provide. It looks like sometime around 11:30pm the computer reset. This morning I'm trying to reinstall all the software that got lost in last night's reset and I get another reset in the middle of compiling. The last message in /var/log/messages before reboot is: Nov 6 10:41:08 trisha ntpd[489]: kernel time sync enabled 6001 Nov 6 10:58:14 trisha ntpd[489]: kernel time sync enabled 2001 Nov 6 13:02:57 trisha syslogd: kernel boot file is /boot/kernel/kernel I just ran memtest86+ and there's no memory errors. I'm guessing it's a hardware issue, but how do I diagnose it? Thanks, Micah