From owner-freebsd-amd64@FreeBSD.ORG  Wed Jan 14 04:58:17 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 15FC116A4CE
	for <freebsd-amd64@FreeBSD.ORG>; Wed, 14 Jan 2004 04:58:17 -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 F11C143D2F
	for <freebsd-amd64@FreeBSD.ORG>;
	Wed, 14 Jan 2004 04:58:15 -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 i0ECwFo8094922
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <freebsd-amd64@FreeBSD.ORG>; Wed, 14 Jan 2004 06:58:15 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0ECwF5p094919;
	Wed, 14 Jan 2004 06:58:15 -0600 (CST)
Date: Wed, 14 Jan 2004 06:58:15 -0600 (CST)
Message-Id: <200401141258.i0ECwF5p094919@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: freebsd-amd64@FreeBSD.ORG
Subject: Re: 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: Wed, 14 Jan 2004 12:58:17 -0000

> From: James Van Artsdalen
> To: freebsd-amd64@FreeBSD.ORG
> Subject: 5.2 RC2 stability?
> 
> Has anyone else has trouble wiith the 5.2 RC2 ISO spontaneously
> rebooting?

This appears to be a false alarm.  The power supply later failed and
no build has failed since it was replaced.

I'm hard pressed to explain why I was able to switch between disks and
repeatably have one fail and the other work over the period of a week
if the power supply was the culprit.  Gremlins do that I guess.
I'm give RC2 24 more hours to fail and then go to 5.2-release.