Date: Sun, 04 Nov 2012 12:32:06 +0100 From: Andre Oppermann <andre@freebsd.org> To: Manfred Antar <null@pozo.com> Cc: Adrian Chadd <adrian@freebsd.org>, freebsd-current@freebsd.org Subject: Re: weird network problems on current since 10/28/2012 Message-ID: <50965236.6040009@freebsd.org> In-Reply-To: <201211040113.qA41DfLn001577@pozo.com> References: <201211031740.qA3HeqVX001622@pozo.com> <CAJ-VmomAR8N8ovhC7La3ttG=7Qu_%2BVwD30tPxFBpzC37eg9CHA@mail.gmail.com> <201211040113.qA41DfLn001577@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04.11.2012 02:13, Manfred Antar wrote: > At 03:29 PM 11/3/2012, Adrian Chadd wrote: >> On 3 November 2012 10:40, Manfred Antar <null@pozo.com> wrote: >>> i have problem connecting to freebsd box on local network since last sunday. >>> the last kernel that works: >>> FreeBSD 10.0-CURRENT #0: Sun Oct 28 12:14:38 PDT 2012 >>> anything after that, sometimes i can connect, other times just hangs. >>> any network connection hangs ===== pop httpd ssh etc etc. >>> anyone have any ideas ? >>> i can checkout different sources and see if i can locate the changes that cause this. >> >> Please do! >> >> >> >> adrian > > OK > Here is what I found doing : > setenv CVSROOT /usr/home/ncvs > > cvs co -D"October 28, 2012 12:14:38 PDT" sys > > A kernel from that time works fine. > > doing: > > cvs up -D"October 28, 2012 13:14:38 PDT" sys 1 hour later > the following files were changed: > sys/netinet/tcp_input.c > sys/netinet/tcp_timer.c > sys/netinet/tcp_var.h > > Building a kernel from these new files is when the problem starts. Can you please provide one or more tcpdump from a failing kernel? Also please enable sysctl net.inet.tcp.logdebug=1 and capture LOG_DEBUG output from syslogd. That may give some important information as well. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50965236.6040009>