From owner-freebsd-isp Tue Oct 10 14:35:30 2000 Delivered-To: freebsd-isp@freebsd.org Received: from blizzard.lightning.net (blizzard.lightning.net [209.51.160.5]) by hub.freebsd.org (Postfix) with ESMTP id E219937B502 for ; Tue, 10 Oct 2000 14:35:22 -0700 (PDT) Received: from nut.lightning.net (nut.lightning.net [209.51.160.16]) by blizzard.lightning.net (8.11.0/8.11.0) with ESMTP id e9ALVVx18374; Tue, 10 Oct 2000 17:31:31 -0400 (EDT) Message-Id: <4.3.2.7.2.20001010171808.04bab6f0@mail.lightning.net> X-Sender: jreddy@mail.lightning.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Oct 2000 17:31:55 -0400 To: freebsd-isp@FreeBSD.ORG From: John Reddy Subject: 3Com 3C509 - packet dropping In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a 3Com 3C509 server NIC that every now and then will simply stop working for approximately 10 - 30 minutes. All throughout this period, I receive the error message: xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! The machine averages about 600kbps in and out, with approximately 3000 to 3500 concurrent connections when this occurs. My question is has anyone seen this problem before? If so, do you know of a fix for this? I've seen this problem before on other versions of FreeBSD in other systems. I know it's not the core OS, because we've pushed similar amounts of bandwidth and connections through other NICs without problem. Either it's the card or the driver. I'd try to look at the driver code if I could, but I'm no coder. -John Reddy -- My public PGP key may be found at http://www.lightning.net/~jreddy John Patrick Reddy Sr. System Administrator Lightning Internet Services, LLC. Tel.(516)248-8400x123 327 Sagamore Ave Pag.(888)935-2700 Mineola, NY 11501 Fax.(516)248-8897 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message