From owner-freebsd-current Fri Nov 1 11:49:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24864 for current-outgoing; Fri, 1 Nov 1996 11:49:41 -0800 (PST) Received: from dcs.stu.rpi.edu (kdupuis@dcs.stu.rpi.edu [128.113.161.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA24853 for ; Fri, 1 Nov 1996 11:49:34 -0800 (PST) Received: from localhost (kdupuis@localhost) by dcs.stu.rpi.edu (8.7.6/8.7.3) with SMTP id OAA02475 for ; Fri, 1 Nov 1996 14:48:56 -0500 (EST) Date: Fri, 1 Nov 1996 14:48:55 -0500 (EST) From: "Kenneth J. Dupuis" To: freebsd-current@freebsd.org Subject: 3c590 problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're seeing really strange behavior on a very fast machine that looks like it has something to do with the networking code. Here's the machine's specs followed by the problem: Intel Endeavor motherboard Intel Pentium 100MHz CPU 512KB cache 32MB EDO RAM 1.0GB Fast SCSI-2 Seagate 51080N hard drive Adaptec 2940U Ultra SCSI PCI controller card 3Com 3c590 10BaseT PCI ethernet card FreeBSD 2.2-961014-SNAP The machine is connected to 10BaseT which goes through an ethernet switch to our 100Mbps FDDI campus backbone. Sustained speeds of 400KB/sec to and from the Internet to this machine are not uncommon for long periods of time. The problem is when someone does an FTP or some other form of a raw transfer into or out of the machine, the networking code seems to hang. The machine becomes "unpingable" and pings from the machine usually result in a "no buffer space available" message. The machine seems to work fine with a standard 16-bit ISA 3c509 card. We've also tried FreeBSD 2.1.5-RELEASE. Any ideas? We need the machine to run with a 3c590, due to the amount of traffic that goes in and out of it. TIA, Kenneth J. Dupuis