From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 20:05:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25DB716A4CE for ; Sun, 23 Jan 2005 20:05:20 +0000 (GMT) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D43A43D2D for ; Sun, 23 Jan 2005 20:05:19 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0NK5HtA023126 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Jan 2005 07:05:18 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0NK5G7l030145; Mon, 24 Jan 2005 07:05:17 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0NK5Glc030144; Mon, 24 Jan 2005 07:05:16 +1100 (EST) (envelope-from pjeremy) Date: Mon, 24 Jan 2005 07:05:16 +1100 From: Peter Jeremy To: Net Virtual Mailing Lists Message-ID: <20050123200515.GB241@cirb503493.alcatel.com.au> References: <20050123135753.14384@mail.net-virtual.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050123135753.14384@mail.net-virtual.com> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 20:05:20 -0000 On Sun, 2005-Jan-23 05:57:53 -0800, Net Virtual Mailing Lists wrote: > It would be nice if somewhere there was >some statement of a "fact" that NIC ____ is known to work well with >FreeBSD. I recall seeing quite a few such statements about different cards over the years. In general, such statements have a limited lifetime because NIC vendors have an ongoing tendency to "improve" their NICs to the point of incompatibility. There are often useful comments about the NICs at the top of the driver code for that NIC (though there's nothing about your AN985). >... after several hours of *HEAVY* (I'm probably understating this) >utilization I get: > >dc0: TX underrun -- increasing TX threshold >dc0: TX underrun -- increasing TX threshold >.. repeats numerous times.. >dc0: TX underrun -- using store and forward mode Real DEC Tulip cards do this when running Tru64 as well. My guess is that it's a bug in the NIC. (And it looks like AMDtek have copied it). >.. at this point the system simply reboots. This is undesirable. However, you have not provided any information that would allow anyone to assist you. Please have a look at http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html > I have attempted to apply a >patch () which I >found which patches sys/pci/if_dcreg.h and sys/pci/if_dc.c. This PR is closed which means that the patches (or functional equivalents) should have already been applied. > I would just like >someone somewhere to tell me what is a stable NIC to use for FreeBSD, I've been using Intel EtherExpress Pro/100+ cards (fxp driver) in some systems where the network gets hammered and haven't had any problems. -- Peter Jeremy