Date: Tue, 29 Apr 2008 14:30:27 +0200 From: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= <peter@pean.org> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: Packet-corruption with re(4) Message-ID: <0DBAF317-2F6E-4492-8700-4CE8216F85DD@pean.org> In-Reply-To: <20080429120834.GB44737@eos.sc1.parodius.com> References: <C94C6F8A-C424-4C7E-955A-5E243BE4FABC@pean.org> <20080429120834.GB44737@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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) I know, I have em in all other machines.. :/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0DBAF317-2F6E-4492-8700-4CE8216F85DD>