From owner-freebsd-stable@FreeBSD.ORG Wed Jun 4 16:39:58 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49E0E37B401 for ; Wed, 4 Jun 2003 16:39:58 -0700 (PDT) Received: from c001.snv.cp.net (h000.c001.snv.cp.net [209.228.32.114]) by mx1.FreeBSD.org (Postfix) with SMTP id 9EA9843F93 for ; Wed, 4 Jun 2003 16:39:57 -0700 (PDT) (envelope-from carlos@reategui.com) Received: (cpmta 8796 invoked from network); 4 Jun 2003 16:39:56 -0700 Received: from 12.33.2.104 (HELO BORABORA) by smtp.register-admin.com (209.228.32.114) with SMTP; 4 Jun 2003 16:39:56 -0700 X-Sent: 4 Jun 2003 23:39:56 GMT Message-ID: <003201c32af2$960aac80$3b0aa8c0@sirf.com> From: "Carlos Reategui" To: "Noor Dawod" References: <20030604161854.M64514@shell.inch.com><000501c32b1c$42bf5560$b655fea9@dawodhome> <20030604230037.GB7355@tuatara.fishballoon.org> Date: Wed, 4 Jun 2003 16:39:47 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4920.2300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 cc: freebsd-stable@freebsd.org Subject: Re: Sudden and unexplained reboots X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 23:39:58 -0000 I would suggest http://www.memtest86.com I had some bad memory on a machine that drove me nuts for several months. I would suggest letting it run through the entire default set of tests. My problem did not show up until test 6 or 7. Since I discovered this I run it religiously on any new machine or one that I have changed the memory on. -Carlos PS. Sorry if this has been suggested already. I saw the thread midstream. > > I shouldn't speculate on causes until you have more idea what's happening, > but this does smell like failing hardware. In your position, I'd be > thinking about swapping RAM and maybe the power supply. > >