From owner-freebsd-stable@FreeBSD.ORG  Thu Nov 27 06:09:10 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C3FA316A4CE; Thu, 27 Nov 2003 06:09:10 -0800 (PST)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id 113C743F85; Thu, 27 Nov 2003 06:09:07 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa31634@salmon>; 27 Nov 2003 14:09:06 +0000 (GMT)
Date: Thu, 27 Nov 2003 14:09:05 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Jonathan Gilpin <jonathan@fluent.ltd.uk>
Message-ID: <20031127140905.GA95486@walton.maths.tcd.ie>
References: <01b401c3b46d$a4ed5cc0$62c4033e@clarity>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01b401c3b46d$a4ed5cc0$62c4033e@clarity>
User-Agent: Mutt/1.5.3i
Sender: dwmalone@maths.tcd.ie
cc: freebsd-bugs@freebsd.org
cc: freebsd-stable@freebsd.org
Subject: Re: 4.9 Stable Crashes on SuperMicro with SMP
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Nov 2003 14:09:10 -0000

On Wed, Nov 26, 2003 at 10:35:49PM -0000, Jonathan Gilpin wrote:
> Further Crashes as reported before:

Both of these crashes could potentially be caused by hardware or
memory problems. While it is possible it's a bug of some sort, I'd
start by checking out my hardware, if I were you...

	David.