From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 02:45:36 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D89616A41F for ; Wed, 5 Oct 2005 02:45:36 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46EA043D45 for ; Wed, 5 Oct 2005 02:45:36 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id C285F19F2C; Tue, 4 Oct 2005 19:50:50 -0700 (PDT) From: "Darren Pilgrim" To: "'Chuck Swiger'" , "'Benjamin Rosenblum'" Date: Tue, 4 Oct 2005 19:45:26 -0700 Message-ID: <000e01c5c956$daca7940$662a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <43429E3B.1080900@mac.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: net@freebsd.org Subject: Which em(4) chips work/don't work? [Was: RE: dummynet, em driver, device polling issues :-((] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 02:45:36 -0000 From: Chuck Swiger > > People who have em NICs, and who do not have problems, probably do not > report regularly that their Intel 10/100/1000 NIC works fine, even > though it does, at least for them. I've got a dozen or so machines > with that hardware, and I haven't seen any problems with them. I'd be interested in finding out the specific chips with which people are (not) having success. As em(4) supports an entire family of products, rather than a single chip, it may be that some chips have quirks or other gotchas the driver needs to address. It certainly wouldn't be the first occurance of revision-specific bugs.