From owner-freebsd-current@FreeBSD.ORG Tue Aug 14 11:20:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F2A116A420 for ; Tue, 14 Aug 2007 11:20:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 05E8213C4A8 for ; Tue, 14 Aug 2007 11:20:12 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id B6D2C1B10EA4; Tue, 14 Aug 2007 13:00:48 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id B3A131B10C26; Tue, 14 Aug 2007 13:00:48 +0200 (CEST) Message-ID: <46C18B60.8050400@moneybookers.com> Date: Tue, 14 Aug 2007 14:00:48 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Eygene Ryabinkin References: <20070806224112.GA21876@muon.bluestop.org> <20070807073920.GV50228@void.codelabs.ru> In-Reply-To: <20070807073920.GV50228@void.codelabs.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: current@freebsd.org Subject: Re: "tcpflags 0x18; tcp_do_segment" kernel messages 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, 14 Aug 2007 11:20:13 -0000 Hi, Eygene Ryabinkin wrote: > Bruce, good day. > > Mon, Aug 06, 2007 at 11:41:12PM +0100, bruce@cran.org.uk wrote: > >> I cvsupped my -CURRENT laptop last night and have been building ports >> today. When I checked the dmesg there were lots of messages similar to: >> >> TCP: [204.152.184.73]:21 to [10.0.10.13]:65159] tcpflags 0x18; >> tcp_do_segment: FIN_WAIT_2: Received data after socket was closed, >> sending RST and removing tcpcb >> > > This was introduced in the /sys/netinet/tcp_input.c, 1.365. > The origin and need for the change was discuissed in > http://lists.freebsd.org/pipermail/freebsd-net/2007-July/014804.html > (See http://lists.freebsd.org/pipermail/freebsd-net/2007-July/014808.html > for the explanation of what's going on). > > If you were running -CURRENT on the same machine prior to CVSupping, > then you probably saw the 'Spurious RST' messages. They were > provoked by the same situation. The messages themselves are harmless, > This is not harmless here :( I'm running current from today 14.Aug. I use an network applications that hangs every time when I see such a message. Any ideas how can I debug, or help to someone who is familiar with the code ? My colleagues report and problems with ssh and apache on this server. > they just telling us that some data was came in, but the listener > had already closed his socket, so he is not interested in the data > anymore. > > Use sys.net.inet.tcp.log_debug to disable TCP stack debug output > and get rid of those. > -- Best Wishes, Stefan Lambrev ICQ# 24134177