From owner-freebsd-current@FreeBSD.ORG Sun Oct 31 22:15:49 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87972106564A for ; Sun, 31 Oct 2010 22:15:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 495518FC14 for ; Sun, 31 Oct 2010 22:15:49 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcEAO+AzUyDaFvO/2dsb2JhbACDCZBEjmqnepEIgSKDL3MEilQ X-IronPort-AV: E=Sophos;i="4.58,268,1286164800"; d="scan'208";a="99119958" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 31 Oct 2010 17:46:57 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 7267EB3F65 for ; Sun, 31 Oct 2010 17:46:57 -0400 (EDT) Date: Sun, 31 Oct 2010 17:46:57 -0400 (EDT) From: Rick Macklem To: freebsd-current@freebsd.org Message-ID: <1060261000.280090.1288561617454.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [99.225.56.115] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - IE8 (Win)/6.0.7_GA_2473.RHEL4_64) Subject: re(4) driver dropping packets when reading NFS files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2010 22:15:49 -0000 I recently purchased a laptop that has a re(4) Realtek 8101E/8102E/8103E net chip in it and I find that it is dropping packets like crazy when reading files over an NFS mount. (It seems that bursts of receive traffic cause it, since when I look over wireshark, typically the 2nd packet in a read reply is not received, although it was sent at the other end.) Adding "options DEVICE_POLLING" helps a lot. (ie. order of magnitude faster reading) Does this hint that interrupts are being lost or delayed too much? Anyhow, if anyone has an idea on what the cause/fix might be or are familiar with the driver/hardware, I'd appreciate hearing about it. Thanks, rick ps: This laptop is running a low end AMD cpu and I did install amd64 on it, instead of i386, in case that might be relevent?