From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 17 19:49:27 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE6D116A418 for ; Mon, 17 Dec 2007 19:49:27 +0000 (UTC) (envelope-from nge@cs.hmc.edu) Received: from knuth.cs.hmc.edu (knuth.cs.hmc.edu [134.173.42.100]) by mx1.freebsd.org (Postfix) with ESMTP id A6E0A13C442 for ; Mon, 17 Dec 2007 19:49:27 +0000 (UTC) (envelope-from nge@cs.hmc.edu) Received: by knuth.cs.hmc.edu (Postfix, from userid 26983) id 410AB85140; Mon, 17 Dec 2007 11:29:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by knuth.cs.hmc.edu (Postfix) with ESMTP id 40A3042F7E0; Mon, 17 Dec 2007 11:29:32 -0800 (PST) Date: Mon, 17 Dec 2007 11:29:32 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@knuth.cs.hmc.edu To: Jordi Espasa Clofent In-Reply-To: <47656FB7.4070807@opengea.org> Message-ID: References: <47656FB7.4070807@opengea.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: Random reboots X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 19:49:27 -0000 On Sun, 16 Dec 2007, Jordi Espasa Clofent wrote: > Hi all, > > I've a couple of this machines [1] in a prduction environment. I suffer > random reboots without any clear reason. > > A possible power failure it's a discarded point: I use a switched rack PDU > and anything is showed by the logs. Moreover, I'm talking about datacenter > environment, so there're a lot of redundant UPSs too. > > So, I tend to think it should be a hard/soft conflict, but when I check the > dmseg and others logs after a random reboot, all appears completely normal. I > know that a kernel dump will be great help, but this boxes has a 4/8GB of > RAM, and their /swap is lesser. That would be especially helpful, since from this information we don't know whether the cause is a kernel panic or a hardware problem. Is your kernel configured to reboot automatically on panic? Also, are you by any chance using the watchdog? -- Nate Eldredge nge@cs.hmc.edu