From owner-freebsd-stable Thu Feb 17 20:34: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id BE83637B7E7 for ; Thu, 17 Feb 2000 20:34:03 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id WAA29348; Thu, 17 Feb 2000 22:33:13 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-87.max1.wa.cyberlynk.net(207.227.118.87) by peak.mountin.net via smap (V1.3) id sma029346; Thu Feb 17 22:32:46 2000 Message-Id: <3.0.3.32.20000217223232.0099c370@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 17 Feb 2000 22:32:32 -0600 To: Omachonu Ogali From: "Jeffrey J. Mountin" Subject: Re: xl0 packet dropping, still Cc: stable@FreeBSD.ORG In-Reply-To: References: <200002171632.LAA07138@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: >I've gotten reports of the 3Com NIC's dropping packets in all OS's using >an Intel CPU, it's more or less a sporadic problem I say... The 3Com's have higher collision rates (tested over long periods) and don't autsense most of the time, which the Intel does much better. Frankly I can't see anyone using a 3Com considering all the problems that crop up on the lists, but then I've been happy with Intel NIC since the Pro100B came out. ;) Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message