From owner-freebsd-current@FreeBSD.ORG  Sun Nov  4 01:14:08 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B4417DA0;
 Sun,  4 Nov 2012 01:14:08 +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 813798FC0C;
 Sun,  4 Nov 2012 01:14:08 +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 qA41DfLn001577
 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT);
 Sat, 3 Nov 2012 18:13:41 -0700 (PDT) (envelope-from null@pozo.com)
Message-Id: <201211040113.qA41DfLn001577@pozo.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 03 Nov 2012 18:13:20 -0700
To: Adrian Chadd <adrian@freebsd.org>
From: Manfred Antar <null@pozo.com>
Subject: Re: weird network problems on current since 10/28/2012
In-Reply-To: <CAJ-VmomAR8N8ovhC7La3ttG=7Qu_+VwD30tPxFBpzC37eg9CHA@mail.g
 mail.com>
References: <201211031740.qA3HeqVX001622@pozo.com>
 <CAJ-VmomAR8N8ovhC7La3ttG=7Qu_+VwD30tPxFBpzC37eg9CHA@mail.gmail.com>
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: qA41DfLn001577
X-pozocom-MailScanner: Found to be clean
X-pozocom-MailScanner-From: null@pozo.com
Cc: freebsd-current@freebsd.org, andre@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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 01:14:08 -0000

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.

========================
||      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.