From owner-freebsd-amd64@FreeBSD.ORG  Mon Dec 17 19:34:35 2007
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
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 63FC416A41B
	for <freebsd-amd64@freebsd.org>; Mon, 17 Dec 2007 19:34:35 +0000 (UTC)
	(envelope-from jordi.espasa@opengea.org)
Received: from mail.opengea.org (234.pool85-48-253.static.orange.es
	[85.48.253.234])
	by mx1.freebsd.org (Postfix) with ESMTP id 157D413C45A
	for <freebsd-amd64@freebsd.org>; Mon, 17 Dec 2007 19:34:35 +0000 (UTC)
	(envelope-from jordi.espasa@opengea.org)
Received: from localhost (tartarus [127.0.0.1])
	by mail.opengea.org (Opengea.org Project MailServer) with ESMTP id
	4CB8BD50038
	for <freebsd-amd64@freebsd.org>; Mon, 17 Dec 2007 20:34:13 +0100 (CET)
X-Virus-Scanned: amavisd-new at opengea.org
Received: from mail.opengea.org ([127.0.0.1])
	by localhost (mail.opengea.org [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id xFGopiwPt7Wa for <freebsd-amd64@freebsd.org>;
	Mon, 17 Dec 2007 20:34:13 +0100 (CET)
Received: from [192.168.1.33] (179.Red-88-25-70.staticIP.rima-tde.net
	[88.25.70.179])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: jordi.espasa@opengea.org)
	by mail.opengea.org (Opengea.org Project MailServer) with ESMTP id
	DC354D50036
	for <freebsd-amd64@freebsd.org>; Mon, 17 Dec 2007 20:34:12 +0100 (CET)
Message-ID: <4766CF56.7030308@opengea.org>
Date: Mon, 17 Dec 2007 20:34:46 +0100
From: Jordi Espasa Clofent <jordi.espasa@opengea.org>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: freebsd-amd64@freebsd.org
References: <47656FB7.4070807@opengea.org>
	<Pine.LNX.4.64.0712171127330.32093@knuth.cs.hmc.edu>
In-Reply-To: <Pine.LNX.4.64.0712171127330.32093@knuth.cs.hmc.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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 <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2007 19:34:35 -0000

> 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?

Yes Nate, I'm working on this way. The idea is attach another HD and 
expand the /swap value and get a coredump file.

Besides of that, I was looking at watchdog but I don't understand their 
operation yet. It's a time question.

-- 
Thanks,
Jordi Espasa Clofent