From owner-freebsd-current@FreeBSD.ORG  Mon Feb 21 10:45:12 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1CFB716A4CF; Mon, 21 Feb 2005 10:45:12 +0000 (GMT)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E405E43D41; Mon, 21 Feb 2005 10:45:11 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with SMTP id 7076B46B37;
	Mon, 21 Feb 2005 05:45:11 -0500 (EST)
Date: Mon, 21 Feb 2005 10:43:36 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: "Conrad J. Sabatier" <conrads@cox.net>
In-Reply-To: <20050220171128.7d1e917e@dolphin.local.net>
Message-ID: <Pine.NEB.3.96L.1050221104251.30083C-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: David Xu <davidxu@freebsd.org>
Subject: Re: AMD64 machine stability problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2005 10:45:12 -0000


On Sun, 20 Feb 2005, Conrad J. Sabatier wrote:

> I've reverted to using a kernel from Sunday, Feb. 13 for the time being. 
> All recent attempts to use newer kernels result in the same problem. 

Including attempts to use a kernel from the 14th?  If you could narrow the
date of the introduction of the problem to a single day, that might be
very helpful.

Thanks,

Robert N M Watson