From owner-freebsd-stable@FreeBSD.ORG Fri Nov 17 13:37:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5F15916A47B for ; Fri, 17 Nov 2006 13:37:05 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E00D43D5C for ; Fri, 17 Nov 2006 13:36:36 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so509258nzh for ; Fri, 17 Nov 2006 05:36:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fzFd+KhQWQpfJb24mZhGJzZEiQ+yhQxRuhRxlsCD0XWE8F57pxVpZxD0RcTAN6gLZBP51t2CkrziLUlq2wziiWDnkh0m122Vif2sC4eApqHrqarJyIDDeoExNXVVtOEUVtKaajtiCNaxUoLsd798cOUmXQhd6r5J6x6mCGpajrw= Received: by 10.65.180.7 with SMTP id h7mr2979267qbp.1163770587793; Fri, 17 Nov 2006 05:36:27 -0800 (PST) Received: by 10.64.204.15 with HTTP; Fri, 17 Nov 2006 05:36:27 -0800 (PST) Message-ID: <84dead720611170536y44477409j3ab56a6a6ab90277@mail.gmail.com> Date: Fri, 17 Nov 2006 19:06:27 +0530 From: "Joseph Koshy" To: "Joe Holden" In-Reply-To: <455D5F38.4060208@joeholden.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <455D5F38.4060208@joeholden.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: (Seemingly) Spontaneous rebooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 13:37:05 -0000 jh> Hi, i'm observing random reboots on a dedicated machine I jh> have with 1&1. jh> I have included as much information as I can think of, if jh> there is anything else I can provide, please ask. Is the machine stable otherwise? Does it pass its builtin diagnostics? A good way to check for bad memory/insufficient cooling is to run a 'make -jN buildworld' repeatedly for 24+hrs, where you choose `N' according to the amount of CPU and RAM you have. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy