From owner-freebsd-isp Thu Oct 12 12:21:54 2000 Delivered-To: freebsd-isp@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C854B37B503 for ; Thu, 12 Oct 2000 12:21:51 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 5B2B61C41; Thu, 12 Oct 2000 15:21:51 -0400 (EDT) Date: Thu, 12 Oct 2000 15:21:51 -0400 From: Bill Fumerola To: Tom Samplonius Cc: John Reddy , freebsd-isp@FreeBSD.ORG Subject: Re: 3Com 3C509 - packet dropping Message-ID: <20001012152151.I37870@jade.chc-chimes.com> References: <4.3.2.7.2.20001010171808.04bab6f0@mail.lightning.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from tom@sdf.com on Thu, Oct 12, 2000 at 09:00:27AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 12, 2000 at 09:00:27AM -0700, Tom Samplonius wrote: > > On Tue, 10 Oct 2000, John Reddy wrote: > > > I've got a 3Com 3C509 server NIC that every now and then will simply stop > ... > > xl0: no memory for rx list -- packet dropped! > > xl0: no memory for rx list -- packet dropped! > > > 3COM 509 + xl is notoriously troublesome. Use an Intel card (fxp > driver) instead. Except the 3com 509 and the xl driver are mutually exclusive. The user has a reliable 3c905 actually and simply (as I already said) needs to tune his network buffers more appropriatly. I've already talked to one of his cohorts(hi gersh) off-list so this is a dead issue (as far as this mailing list is concerned). -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message