From owner-freebsd-current@FreeBSD.ORG Tue Jun 12 17:15:32 2007 Return-Path: X-Original-To: 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 5DB4516A46E for ; Tue, 12 Jun 2007 17:15:32 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id B05AE13C487 for ; Tue, 12 Jun 2007 17:15:31 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 3659 invoked from network); 12 Jun 2007 16:29:03 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 12 Jun 2007 16:29:03 -0000 Message-ID: <466ED4B4.30909@freebsd.org> Date: Tue, 12 Jun 2007 19:15:32 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Eygene Ryabinkin References: <20070611140644.GH86872@void.codelabs.ru> <466D9DDE.6090302@freebsd.org> <20070612032656.GJ86872@void.codelabs.ru> <20070612033432.GK86872@void.codelabs.ru> In-Reply-To: <20070612033432.GK86872@void.codelabs.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: shigeaki@f.csce.kyushu-u.ac.jp, freebsd-net@freebsd.org, freebsd-current@freebsd.org, yongari@freebsd.org Subject: Re: nfe(4) strangeness on the 7-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 12 Jun 2007 17:15:32 -0000 Eygene Ryabinkin wrote: > Me again. > > Tue, Jun 12, 2007 at 07:26:56AM +0400, Eygene Ryabinkin wrote: >> Mon, Jun 11, 2007 at 09:09:18PM +0200, Andre Oppermann wrote: >>> These messages are unrelated to your hardware. There you can relax. >>> We have a bug in the TCP FSM state transitions which I'm currently >>> tracking down that indirectly causes the log messages. You don't >>> have to worry about it for your case. TCP connections work fine. >> OK, thank you! > > Just checked my netstat output and spotted weird lines: > ----- > tcp4 0 0 127.0.0.1.* 127.0.0.1.40001 CLOSED > tcp4 0 0 127.0.0.1.* 127.0.0.1.40001 CLOSED > ----- > Can they be related to the bug you mentioned? Yes, this looks related. Do these line stick around or do they go away after some time? -- Andre