From owner-freebsd-current@FreeBSD.ORG Wed May 30 12:39:59 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 0484316A400 for ; Wed, 30 May 2007 12:39:59 +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 6A29D13C45E for ; Wed, 30 May 2007 12:39:58 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 14086 invoked from network); 30 May 2007 11:55:57 -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 ; 30 May 2007 11:55:57 -0000 Message-ID: <465D70A4.3040107@freebsd.org> Date: Wed, 30 May 2007 14:40:04 +0200 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Steve Kargl References: <20070525234115.GA48789@troutmask.apl.washington.edu> <465AF5C6.2010302@freebsd.org> <20070529002304.GA90534@troutmask.apl.washington.edu> In-Reply-To: <20070529002304.GA90534@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Segment failed SYNCOOKIE? 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: Wed, 30 May 2007 12:39:59 -0000 Steve Kargl wrote: > On Mon, May 28, 2007 at 05:31:18PM +0200, Andre Oppermann wrote: >> Steve Kargl wrote: >>> Anyone have ideas on how to cure >>> >>> May 25 16:20:03 node13 kernel: TCP: [192.168.0.15]:53815 to >>> [192.168.0.13]:50992 tcpflags 0x11; syncache_expand: >>> Segment failed SYNCOOKIE authentication >>> >>> The hardware and kernel on 192.168.0.15 and 192.168.0.13 >>> are identical. >> Do you have any daemon listening on [192.168.0.13]:50992? >> > > I've set "net.inet.tcp.syncookies=0" in /boot/loader.conf > to disable syncookies. I'm now seeing > >> May 28 16:39:59 node13 kernel: bge0: watchdog timeout -- resetting >> May 28 16:39:59 node13 kernel: bge0: link state changed to DOWN >> May 28 16:40:02 node13 kernel: bge0: link state changed to UP >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.13]:62460 to >> [192.168.0.13]:56460 tcpflags 0x10; syncache_expand: Spurious ACK >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.13]:64274 to >> [192.168.0.13]:49985 tcpflags 0x10; syncache_expand: Spurious ACK >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.11]:51473 to >> [192.168.0.13]:57885 tcpflags 0x11; syncache_expand: Spurious ACK >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.12]:49393 to >> [192.168.0.13]:57885 tcpflags 0x10; syncache_expand: Spurious ACK >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.12]:61494 to >> [192.168.0.13]:52887 tcpflags 0x10; syncache_expand: Spurious ACK >> May 28 16:41:51 node13 kernel: TCP: [192.168.0.12]:63379 to >> [192.168.0.13]:63472 tcpflags 0x10; syncache_expand: Spurious ACK > > This is occurring with an openmpi application. I have committed further changes and logging to tcp_input() that will give more insight into this. Please update to the latest current and report the new log messages. -- Andre