From owner-freebsd-net@FreeBSD.ORG Thu Sep 10 01:30:06 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 583481065670 for ; Thu, 10 Sep 2009 01:30:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 472A58FC0C for ; Thu, 10 Sep 2009 01:30:06 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8A1U6fc077699 for ; Thu, 10 Sep 2009 01:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8A1U6Es077696; Thu, 10 Sep 2009 01:30:06 GMT (envelope-from gnats) Date: Thu, 10 Sep 2009 01:30:06 GMT Message-Id: <200909100130.n8A1U6Es077696@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Bruce Cran Cc: Subject: Re: kern/64556: [sis] if_sis short cable fix problems with NetGear FA311's X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 01:30:06 -0000 The following reply was made to PR kern/64556; it has been noted by GNATS. From: Bruce Cran To: bug-followup@FreeBSD.org, tom@hur.st Cc: Subject: Re: kern/64556: [sis] if_sis short cable fix problems with NetGear FA311's Date: Thu, 10 Sep 2009 02:24:17 +0100 I'm still seeing this problem on 8.0-BETA4. Running two ttcp's (one rx, one tx) causes the system to print lots of "Applying short cable fix" messages. I've had a look through the NetBSD driver, the original Linux driver from http://www.soekris.com/downloads.htm and also the latest Linux sources. When the issue occurs, I see throughput drop to around 5Mb. The first issues seems to be the 100ms delay. From the other code I've looked at, it looks like it should be 100us which would speed up the reset process. Secondly, it seems that only FreeBSD resets the chip when an RX overrun occurs; on NetBSD it does a printf and continues, and Linux increments the error statistics. Both only apply the short cable fix when a media change occurs. -- Bruce Cran