From owner-freebsd-current@FreeBSD.ORG  Wed May 19 11:33:29 2004
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 3C09C16A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 19 May 2004 11:33:29 -0700 (PDT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9BCCA43D3F
	for <freebsd-current@freebsd.org>;
	Wed, 19 May 2004 11:33:28 -0700 (PDT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <KYKJYPMH>; Wed, 19 May 2004 14:33:13 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337051D8CAE@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: 'Tom Kiblin' <tom@kiblin.com>, freebsd-current@freebsd.org
Date: Wed, 19 May 2004 14:33:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Stability issues with 5.2.1 p4
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: Wed, 19 May 2004 18:33:29 -0000

From: Tom Kiblin [mailto:tom@kiblin.com]
> 
> Hello,
> 
> I am running a dual xeon with hyperthreading, SCSI system, that
> constantly crashes under load.  The box is doing about 40mbs of
> transfer, and I get a panic with the following output on the screen:
> 
> 
> http://advancedhosters.com/zico.JPG
> 
> Any ideas or suggestions?
> 

You probably want to look @ turning on crash-dumps
(rc.conf, set dumpdev), making sure you have enough swap
to hold all physical memory, and then debugging the
core that comes out.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld
ebug.html
has instructions.

If you post back a stack trace from this process,
you'll likely get more responses.

--don