From owner-freebsd-stable@FreeBSD.ORG Tue Apr 29 12:45:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38ED61065675; Tue, 29 Apr 2008 12:45:58 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 248678FC15; Tue, 29 Apr 2008 12:45:58 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 18CA41CC033; Tue, 29 Apr 2008 05:45:58 -0700 (PDT) Date: Tue, 29 Apr 2008 05:45:58 -0700 From: Jeremy Chadwick To: Peter =?iso-8859-1?Q?Ankerst=E5l?= Message-ID: <20080429124558.GA46018@eos.sc1.parodius.com> References: <20080429120834.GB44737@eos.sc1.parodius.com> <0DBAF317-2F6E-4492-8700-4CE8216F85DD@pean.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0DBAF317-2F6E-4492-8700-4CE8216F85DD@pean.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: Packet-corruption with re(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2008 12:45:58 -0000 On Tue, Apr 29, 2008 at 02:30:27PM +0200, Peter Ankerstål wrote: > > On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote: >>> >> >> tcpdump reporting "bad cksum" can occur due to TX/RX checksum >> offloading. Do you not see this message normally, but only when the >> problem begins? >> >> Have you tried turning off TX/RX offloading to see if the erroneous >> behaviour goes away? >> >> Have you tried disabling RFC1323 to see if that's actually what's >> responsible for the stalls you're seeing? sysctl net.inet.tcp.rfc1323=0 >> >> I'd recommend staying away from Realtek NICs. Pick up an Intel Pro/1000 >> GT or PT. Realtek has a well-known history of issues. >> > > Now Ive tried: > ninja# sysctl net.inet.tcp.rfc1323=0 > net.inet.tcp.rfc1323: 1 -> 0 > ninja# ifconfig re0 -rxcsum -txcsum -tso -lro > > The problem remains, but when I have -rxcsum/tx tcpdump does not say > anything > about bad checksums but it send out the same ack over and over. > and it seems like bigger files are the most effected (images rather then > html-files) Okay, so the problem is likely not with checksums, but more of a problem with network I/O suddenly stopping for no apparent reason. Have you tried disabling MSI/MSI-X via /boot/loader.conf to see if that makes any difference? I wonder if somehow interrupts are no longer firing for the re(4) card. Try putting these in loader.conf and rebooting: hw.pci.enable_msi="0" hw.pci.enable_msix="0" Otherwise, I think Pyun YongHyeon might have some better ideas. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |