From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 12 15:34:44 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AE4B16A4CE for ; Sat, 12 Mar 2005 15:34:44 +0000 (GMT) Received: from S4.cableone.net (smtp4.cableone.net [24.116.0.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id D986543D2D for ; Sat, 12 Mar 2005 15:34:43 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.local.lan (unverified [24.119.71.105]) by S4.cableone.net (CableOne SMTP Service S4) with ESMTP id 12936568 for multiple; Sat, 12 Mar 2005 08:41:37 -0700 Date: Sat, 12 Mar 2005 09:33:45 -0600 From: Vulpes Velox To: Ben Haysom Message-ID: <20050312093345.233739c4@vixen42.local.lan> In-Reply-To: References: X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 0, First 1, in=3, out=0, spam=0 X-External-IP: 24.119.71.105 X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: freebsd-hardware@freebsd.org Subject: Re: Unclean Reboot For No Apparent Reason X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2005 15:34:44 -0000 On Mon, 7 Mar 2005 17:29:17 +0000 Ben Haysom wrote: > Hi > > A while ago I asked about my 5.3 machine which has taken to > rebooting itself during a full portupgrade.Doesn't shut down > properly - just resets. > > I was advised to try a few things. > > I've done memtest86 from CD, let it do 5 passes and it found no > problems. I unplugged both CDs and the Floppy, and tried it, but > still did the same. cpuburn seems fine. > doing mbmon whilst executing the portupgrade -a command shows the > temperature get to around 42.5 before it resets, but it can vary. > > I'm stuck now... any ideas? > Ben Haysom Memory tests only proove that that the memory is good, not that the hardware the ram is connected to is good. The same for cpuburn. The best stress test is running a make buildword, a make install for scilab, and a find /. If that does not do it, it is most likely a intermitently flakey power supply.