From owner-freebsd-hackers Wed Mar 22 21:16:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 7478337BA17 for ; Wed, 22 Mar 2000 21:16:22 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id VAA19172; Wed, 22 Mar 2000 21:16:07 -0800 (PST) Date: Wed, 22 Mar 2000 21:16:07 -0800 From: Brooks Davis To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NCR/FXP and coredumps Message-ID: <20000322211607.A7582@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from dmiller@search.sparks.net on Wed, Mar 22, 2000 at 10:50:47PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 22, 2000 at 10:50:47PM -0500, David Miller wrote: > Two item: > > 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. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message