From owner-freebsd-scsi Wed May 29 14:17:57 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08014 for freebsd-scsi-outgoing; Wed, 29 May 1996 14:17:57 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07975; Wed, 29 May 1996 14:17:37 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id OAA00340; Wed, 29 May 1996 14:17:28 -0700 Date: Wed, 29 May 1996 14:17:28 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "Andrew V. Stesin" cc: questions@freebsd.org, scsi@freebsd.org Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) In-Reply-To: <199605281649.TAA07502@office.elvisti.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Andrew V. Stesin wrote: > When a Compex ReadyLink (DEC 21041-based) PCI ethernet was replaced > by a random NE2000, the trouble almost gone -- the box was up for > some days, just Ok. Someone has noted that recent Compex's don't work well with FreeBSD. That may clear up some of your random crashes. > 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. I wonder if you have a resource conflict between the NCR and your ethernet card. My NCR may be broke but I had to manually set the IRQ in the PC BIOS. Make sure that the ethernet card and the NCR aren't sharing resources. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major