From owner-freebsd-amd64@FreeBSD.ORG  Sat Jan 10 01:21:36 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BDA6B16A4CE
	for <freebsd-amd64@FreeBSD.ORG>; Sat, 10 Jan 2004 01:21:36 -0800 (PST)
Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com
	[24.73.246.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 48F6243D62
	for <freebsd-amd64@FreeBSD.ORG>;
	Sat, 10 Jan 2004 01:21:30 -0800 (PST)
	(envelope-from james@bigtex.jrv.org)
Received: from bigtex.jrv.org (localhost [127.0.0.1])
	by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i0A9LTo8021506
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <freebsd-amd64@FreeBSD.ORG>; Sat, 10 Jan 2004 03:21:29 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0A9LTa9021503;
	Sat, 10 Jan 2004 03:21:29 -0600 (CST)
Date: Sat, 10 Jan 2004 03:21:29 -0600 (CST)
Message-Id: <200401100921.i0A9LTa9021503@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: freebsd-amd64@FreeBSD.ORG
Subject: 5.2 RC2 stability?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
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: Sat, 10 Jan 2004 09:21:36 -0000

Has anyone else has trouble wiith the 5.2 RC2 ISO spontaneously
rebooting?

The older 5.2beta gave me no trouble at all, nor did a cvsup on 12/15.
But the 5.2 RC2 ISO will reboot, with no kernel panic or other serial
port output, after heavy activity.  A loop running "make buildworld"
won't run more than 24 hours or so.

I put the 12/15 disk back on the system and it rusn fine - it doesn't
seem to be any motherboard degradation or such.