From owner-freebsd-scsi Thu May 30 03:20:24 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA21281 for freebsd-scsi-outgoing; Thu, 30 May 1996 03:20:24 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA20590; Thu, 30 May 1996 03:16:02 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id NAA06287; Thu, 30 May 1996 13:17:16 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id NAA16958; Thu, 30 May 1996 13:17:11 +0300 From: "Andrew V. Stesin" Message-Id: <199605301017.NAA16958@office.elvisti.kiev.ua> Subject: Re: Mysterious crashes of FreeBSD gateway -- caugh it(?) To: dwhite@resnet.uoregon.edu Date: Thu, 30 May 1996 13:17:11 +0300 (EET DST) Cc: stesin@elvisti.kiev.ua, questions@freebsd.org, scsi@freebsd.org In-Reply-To: from "Doug White" at May 29, 96 02:17:28 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text 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. Yes, indeed. Compex ReadyLink Rev. D1 worked (and still works) perfectly; Rev.D2 -- problems... # > 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. I doubt. Ether (NE2000) is on ISA port 0x280 irq 5 -- nothing even close to NCR. # My NCR may be broke but I had to manually set the IRQ in # the PC BIOS. Yes, I do it always by hand (NCR uses a jumper-settable PCI INT, by default -- INT A. I don't know details, but from my experience it's wise to set NCR's PCI slot to use INT A manually; problems otherwise). # Make sure that the ethernet card and the NCR aren't sharing # resources. Is it possible at all? # # Doug White | University of Oregon # Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant # http://gladstone.uoregon.edu/~dwhite | Computer Science Major # -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1.