From owner-freebsd-stable@FreeBSD.ORG Tue Apr 29 12:08:34 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 A9122106566B for ; Tue, 29 Apr 2008 12:08:34 +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 93D118FC15 for ; Tue, 29 Apr 2008 12:08:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 8BCDE1CC033; Tue, 29 Apr 2008 05:08:34 -0700 (PDT) Date: Tue, 29 Apr 2008 05:08:34 -0700 From: Jeremy Chadwick To: Peter =?iso-8859-1?Q?Ankerst=E5l?= Message-ID: <20080429120834.GB44737@eos.sc1.parodius.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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:08:34 -0000 On Tue, Apr 29, 2008 at 01:18:10PM +0200, Peter Ankerstål wrote: > Im using a built in re(4) card and it seems like its causes data-corruption > as soon as it gets some load (or after a few hours online) > > The machine is running FreeBSD 7.0R: > > FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Apr 16 22:49:15 CEST > 2008 peter@ninja:/usr/obj/usr/src/sys/NINJA amd64 > > (using a RELENG_7 kernel updated today) > > > If I download alot of files with wget or something everything works fine > for a while until the download just stalls and tcpdump reports "bad cksum" > > 13:04:25.839408 IP (tos 0x0, ttl 64, id 23912, offset 0, flags [DF], proto > TCP (6), length 1500, bad cksum 0 (->f40a)!) host1.http > host2.53895: . > 115065:116513(1448) ack 1421 win 8326 2174233192> > and so on > again and again until the connection times out. 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. -- | 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 |