From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 14:59:17 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 D223116A418 for ; Fri, 21 Sep 2007 14:59:17 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4579A13C4AA for ; Fri, 21 Sep 2007 14:59:17 +0000 (UTC) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (holub.ics.muni.cz [147.251.23.83]) (authenticated user=hopet@ICS.MUNI.CZ bits=0) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id l8LExF6e005252 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 21 Sep 2007 16:59:15 +0200 From: "Petr Holub" To: "Jeremy Chadwick" Date: Fri, 21 Sep 2007 16:59:16 +0200 Message-ID: <004901c7fc5f$fb269190$5317fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 In-Reply-To: <20070921133316.GA63294@eos.sc1.parodius.com> Importance: Normal X-Muni-Spam-TestIP: 147.251.23.83 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Envelope-To: current@FreeBSD.org X-Muni-Virus-Test: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Fri, 21 Sep 2007 16:59:15 +0200 (CEST) X-Mailman-Approved-At: Mon, 24 Sep 2007 08:18:03 +0000 Cc: current@FreeBSD.org Subject: RE: TCP socket problem on Sept. -CURRENT snapshot 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: Fri, 21 Sep 2007 14:59:17 -0000 > > It occurred from several different addresses and results in being > > unable event to ping that IP until reboot. > > This is "normal" for the current time being, as the output in question > is being used to help track down a TCP-related bug in -CURRENT: Thank you! Actually, the more painful problem is that it made some IP addresses unreachable afterwards: I was unable to ping them, to make any TCP connection, etc. Though I was unable to ping (almost all) other IPs and I was also able to ping/connect those ``stuck'' IPs from another host siting on the same network. So it looks like the problem is actually some per-IP bug... Any reports of this behavior reported before before I start looking into this deeper? Just for reference, I'm using 200709 snapshot of 7.0-CURRENT for amd64, running on Core2 Duo with a custom kernes with WITNESS turned off. Thanks, Petr