From owner-freebsd-hardware@FreeBSD.ORG  Thu Jul 31 12:58:56 2003
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 706C737B40C
	for <freebsd-hardware@freebsd.org>;
	Thu, 31 Jul 2003 12:58:56 -0700 (PDT)
Received: from wrongcrowd.com (dsl231-036-178.sea1.dsl.speakeasy.net
	[216.231.36.178])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 243E743FD7
	for <freebsd-hardware@freebsd.org>;
	Thu, 31 Jul 2003 12:58:55 -0700 (PDT)
	(envelope-from matt@wrongcrowd.com)
Received: from matt (helo=localhost)
	by wrongcrowd.com with local-esmtp (Exim 3.34 #1)
	id 19iJZb-000KTU-00
	for freebsd-hardware@freebsd.org; Thu, 31 Jul 2003 12:58:51 -0700
Date: Thu, 31 Jul 2003 12:58:51 -0700 (PDT)
From: Matt Staroscik <matt@wrongcrowd.com>
To: freebsd-hardware@freebsd.org
In-Reply-To: <20030731190138.8407C37B405@hub.freebsd.org>
Message-ID: <20030731125135.E77421-100000@wrongcrowd.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: signal 11
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2003 19:58:58 -0000


>Suggestions? If you think it's marginal HW, do you have any
>suggestions on how to test and determine the culprit?

I would approach it this way:

- Wiggle all cables, reseat all components (you never know...)
- Check CPU cooling (I had CPU-related sig 11 crashes once myself)
- If CPU cooling is OK, try underclocking the CPU; if it is marginal this
may make it stable, and then you will know.
- Swap in a different power supply (a flaky PS can do all KIND of weird
things.)
- Swap in different RAM (or test RAM with memtest86)

If you can rule out CPU, RAM, PS... post a followup.

Good luck!