Date: Wed, 29 May 1996 22:55:46 +0200 (MET DST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: stesin@elvisti.kiev.ua (Andrew V. Stesin) Cc: questions@freebsd.org, scsi@freebsd.org Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) Message-ID: <199605292055.WAA11549@yedi.iaf.nl> In-Reply-To: <199605281649.TAA07502@office.elvisti.kiev.ua> from "Andrew V. Stesin" at May 28, 96 07:49:10 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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 --------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605292055.WAA11549>