From owner-freebsd-current@FreeBSD.ORG Tue May 29 00:24:49 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 C583316A4CD; Tue, 29 May 2007 00:24:49 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id A914513C483; Tue, 29 May 2007 00:24:49 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id l4T0N4Y9090561; Mon, 28 May 2007 17:23:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id l4T0N4Uo090560; Mon, 28 May 2007 17:23:04 -0700 (PDT) (envelope-from sgk) Date: Mon, 28 May 2007 17:23:04 -0700 From: Steve Kargl To: Andre Oppermann Message-ID: <20070529002304.GA90534@troutmask.apl.washington.edu> References: <20070525234115.GA48789@troutmask.apl.washington.edu> <465AF5C6.2010302@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465AF5C6.2010302@freebsd.org> User-Agent: Mutt/1.4.2.2i 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: Tue, 29 May 2007 00:24:49 -0000 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. -- Steve