From owner-freebsd-scsi  Wed May 29 14:40:14 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA09794
          for freebsd-scsi-outgoing; Wed, 29 May 1996 14:40:14 -0700 (PDT)
Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09676;
          Wed, 29 May 1996 14:39:54 -0700 (PDT)
Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA13337; Wed, 29 May 1996 23:37:35 +0200
Received: by uni4nn.iaf.nl with UUCP id AA18315
  (5.67b/IDA-1.5); Wed, 29 May 1996 23:34:13 +0200
Received: by iafnl.es.iaf.nl with UUCP id AA23147
  (5.67b/IDA-1.5); Wed, 29 May 1996 23:11:59 +0200
Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id WAA11549; Wed, 29 May 1996 22:55:46 +0200
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199605292055.WAA11549@yedi.iaf.nl>
X-Organisation: Private FreeBSD site - Arnhem - The Netherlands
Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?)
To: stesin@elvisti.kiev.ua (Andrew V. Stesin)
Date: Wed, 29 May 1996 22:55:46 +0200 (MET DST)
Cc: questions@freebsd.org, scsi@freebsd.org
In-Reply-To: <199605281649.TAA07502@office.elvisti.kiev.ua> from "Andrew V. Stesin" at May 28, 96 07:49:10 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Andrew V. Stesin wrote...

> When doing a massive TCP transfers to the 1.1.5-connected subnet,
> or even ping -f, a high network load was inspired on a gateway
> machine (receive a packet -- forvard it -- send redirect).
> NE2000 worked fine, but NCR driver started to through messages
> about I/O errors, "NCR dead", etc.  Then gateway rebooted itself.
> 
> 	What I want to ask.
> 
> What might be the source of that trouble? Poor motherboard quality, when
> an overloaded (?! is it an overload?) either ISA or PCI bus forces NCR
> to go asleep?  Or is it a bug in TCP/IP stack or IPfilter, or
> their interraction with NCR driver, tickled
> with the nessesity to process IP/ICMP packets at a very high rate?

> I strongly suspect a hardware problem, but maybe there are other
> opinions?

I have also seen this happen with a SCSI device that was not 'liked'
by the ncr driver. After changing the firmware of the _device_ (a tape)
the problem went away. 

A 'dead' ncr is a perfectly acceptable reason for the system to reboot
itself (at least it was on mine).

I admit this does not correlate well with your ethernet board swapping,
but it is another datapoint on 'dead' ncrs

Wilko
_     __________________________________________________________________________
 |   / o / /  _   Wilko Bulte             email: wilko@yedi.iaf.nl
 |/|/ / / /( (_)  Private FreeBSD site  - Arnhem - The Netherlands
--------------------------------------------------------------------------------