From owner-freebsd-hackers  Wed Mar 22 23:58:38 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by hub.freebsd.org (Postfix) with SMTP id 93B2F37B956
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 22 Mar 2000 23:58:31 -0800 (PST)
	(envelope-from sthaug@nethelp.no)
Received: (qmail 36765 invoked by uid 1001); 23 Mar 2000 07:58:28 +0000 (GMT)
To: brooks@one-eyed-alien.net
Cc: dmiller@search.sparks.net, freebsd-hackers@FreeBSD.ORG
Subject: Re: NCR/FXP and coredumps
From: sthaug@nethelp.no
In-Reply-To: Your message of "Wed, 22 Mar 2000 21:16:07 -0800"
References: <20000322211607.A7582@orion.ac.hmc.edu>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Thu, 23 Mar 2000 08:58:28 +0100
Message-ID: <36763.953798308@verdi.nethelp.no>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 1) I managed to crash an intel N440BX mobo with an fxp card and the
> > onboard ncr drivers.  Lots of network traffic (ping floods) and disk IO
> > (rawio in parallel on two disks) took it down in something like two
> > hours. I know this is a known bug, I'm just offering core dumps and
> > testing services in fixing it if anyone wants to take a stab at it.
> 
> DG has looked at this extensively and the current feeling is that this is
> a hardware bug.  Using the sym driver instead of the ncr driver
> apparently helps somewhat, but the problem still happens.  The generally
> recommended option is to buy an Adaptec SCSI controller and use that
> instead of the on-board SCSI.  That works flawlessly.

I can confirm that the sym driver has cured all such problems for us.
Not a single crash after switching to the sym driver.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message