From owner-freebsd-stable Thu Feb 17 4:51:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id 485E837B6B6 for ; Thu, 17 Feb 2000 04:51:42 -0800 (PST) (envelope-from root@boostworks.com) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id NAA89047; Thu, 17 Feb 2000 13:51:18 +0100 (CET) Message-Id: <200002171251.NAA89047@luxren2.boostworks.com> Date: Thu, 17 Feb 2000 13:51:10 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@boostworks.com Subject: Re: xl0 packet dropping, still To: cokane@one.net Cc: stable@FreeBSD.ORG In-Reply-To: <20000216161953.A5237@evil.2y.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Feb, Coleman Kane was caught persisting on: > Can this be fixed, or is it caused by a deficiency in the hardware? > > --cokane > Wait for 4.0 to have it fixed or the fix MFC'ed to stable. From a personal POV, I have got too much problems with 3com like cards that i now let Win$ users suffer with that brand (anyway, they keep going stealing me good cards when I'm not looking). I would recommand that you switch to an (Ex-)Digital 2114x or Intel 8255[89] based one. I would favor the Intel chip since it provides the lowest level of interrupts/packets processed, hence a lower system load. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message