From owner-freebsd-current@FreeBSD.ORG Mon Nov 5 01:49:05 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B49DAD83; Mon, 5 Nov 2012 01:49:05 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.freebsd.org (Postfix) with ESMTP id 743A88FC0C; Mon, 5 Nov 2012 01:49:05 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.5/8.14.5) with ESMTP id qA51daHj019870 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Sun, 4 Nov 2012 17:39:42 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <201211050139.qA51daHj019870@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 04 Nov 2012 17:39:10 -0800 To: Andre Oppermann From: Manfred Antar Subject: Re: weird network problems on current since 10/28/2012 In-Reply-To: <5096E4D4.6000000@freebsd.org> References: <201211031740.qA3HeqVX001622@pozo.com> <201211040113.qA41DfLn001577@pozo.com> <50964FBB.4010600@andric.com> <50967453.5090503@freebsd.org> <5096CCDE.7090305@fgznet.ch> <5096E4D4.6000000@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,MISSING_MID autolearn=no version=3.3.2, No X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: qA51daHj019870 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 05 Nov 2012 01:49:05 -0000 At 01:57 PM 11/4/2012, you wrote: >On 04.11.2012 21:15, Andreas Tobler wrote: >>On 04.11.12 14:57, Andre Oppermann wrote: >>>On 04.11.2012 13:11, Kim Culhan wrote: >>>>On Sun, November 4, 2012 6:21 am, Dimitry Andric wrote: >>>>>On 2012-11-04 02:13, Manfred Antar wrote: >>>>>>At 03:29 PM 11/3/2012, Adrian Chadd wrote: >>>>>After the commit, there was a small discussion thread on svn-src-head@ >>>>>about the possible problems with the approach. Maybe you are >>>>>experiencing those? >>>>> >>>>>As the commit message says, you should be able to turn the feature off >>>>>using: >>>>> >>>>> sysctl net.inet.tcp.experimental.initcwnd10=0 >>>>> >>>>>Can you please try that, and see if the problems go away? >>>> >>>>FWIW this did not make the problem go away on 2 machines. >>> >>>Yes, this very much looks like the same problem as in PR/173309. >>> >>>Please try the attached patch. It fixes the connection hang issue. >>>There may be a second issue I debugging currently base on the feedback >>>from Fabian Keil. >> >>I jump into this thread since I have a similar network issue. >> >>My scenario: >> >>'make installkernel DESTDIR=/netboot/test' to a nfs mounted drive. >>The nfs drive on the server is an ufs fs. No zfs. >> >>Up to r242261 I can install the kernel (or world) in a fluent way to the >>nfs destination. >> >>>From r242262 it doesn't work smooth. I have stalls, sometimes my >>patience is not enough and I kill the process. >> >>I tried 242266 with the above mentioned patch. No real success. >> >>How can I help/test? > >Please try the attach patch instead of the above mentioned one. > >-- >Andre > >Index: netinet/tcp_output.c >=================================================================== >--- netinet/tcp_output.c (revision 242577) >+++ netinet/tcp_output.c (working copy) >@@ -228,7 +228,7 @@ > tso = 0; > mtu = 0; > off = tp->snd_nxt - tp->snd_una; >- sendwin = min(tp->snd_wnd, tp->snd_cwnd); >+ sendwin = ulmax(ulmin(tp->snd_wnd - off, tp->snd_cwnd), 0); > > flags = tcp_outflags[tp->t_state]; > /* >@@ -249,7 +249,7 @@ > (p = tcp_sack_output(tp, &sack_bytes_rxmt))) { > long cwin; > >- cwin = min(tp->snd_wnd, tp->snd_cwnd) - sack_bytes_rxmt; >+ cwin = ulmin(tp->snd_wnd - off, tp->snd_cwnd) - sack_bytes_rxmt; > if (cwin < 0) > cwin = 0; > /* Do not retransmit SACK segments beyond snd_recover */ >@@ -355,7 +355,7 @@ > * sending new data, having retransmitted all the > * data possible in the scoreboard. > */ >- len = ((long)ulmin(so->so_snd.sb_cc, tp->snd_wnd) >+ len = ((long)ulmin(so->so_snd.sb_cc, tp->snd_wnd - off) > - off); > /* > * Don't remove this (len > 0) check ! This doesn't seem to make a difference. I have a ssh window thats been trying to connect for the past 5 minutes. This is on a local network 192.168.0.4 >===========SSH==============> 192.168.0.5 Also pop from the same machines endless trying to connect. Hopefully this mail will get thru , otherwise i will need to reboot to old kernel Manfred ======================== || null@pozo.com || || Ph. (415) 681-6235 || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.