From owner-freebsd-net@FreeBSD.ORG Wed Oct 5 02:48:29 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 567D216A41F for ; Wed, 5 Oct 2005 02:48:29 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from mta5.srv.hcvlny.cv.net (mta5.srv.hcvlny.cv.net [167.206.4.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7764B43D6B for ; Wed, 5 Oct 2005 02:48:21 +0000 (GMT) (envelope-from ben@benswebs.com) Received: from [127.0.0.1] (ool-18bbf604.dyn.optonline.net [24.187.246.4]) by mta5.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-2.06 (built May 11 2005)) with ESMTP id <0INV00A9294KRSC1@mta5.srv.hcvlny.cv.net> for net@freebsd.org; Tue, 04 Oct 2005 22:48:21 -0400 (EDT) Date: Tue, 04 Oct 2005 22:48:31 -0400 From: Benjamin Rosenblum In-reply-to: <000e01c5c956$daca7940$662a15ac@smiley> To: net@freebsd.org Message-id: <43433EFF.8040007@benswebs.com> MIME-version: 1.0 X-Accept-Language: en-us, en References: <000e01c5c956$daca7940$662a15ac@smiley> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: 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:48:29 -0000 my non working card is 82547EI aka 1000CT. Darren Pilgrim wrote: >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. > > > > > >