From owner-freebsd-current@FreeBSD.ORG Thu May 26 02:48:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D27C1065673; Thu, 26 May 2011 02:48:54 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail.sippysoft.com (mail.sippysoft.com [4.59.13.245]) by mx1.freebsd.org (Postfix) with ESMTP id 660DD8FC1B; Thu, 26 May 2011 02:48:54 +0000 (UTC) Received: from [4.59.13.245] (helo=[192.168.1.79]) by mail.sippysoft.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QPQ97-0009lp-LZ; Wed, 25 May 2011 19:17:57 -0700 Message-ID: <4DDDB854.50306@FreeBSD.org> Date: Wed, 25 May 2011 19:17:56 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Daniel Gerzo References: <4DDD4890.70604@FreeBSD.org> <4DDD4964.7060008@sippysoft.com> <4DDD537A.7090408@FreeBSD.org> In-Reply-To: <4DDD537A.7090408@FreeBSD.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Sender: sobomax@sippysoft.com X-ssp-trusted: yes Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek , Mikolaj Golub Subject: Re: Weird issue with hastd(8) 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: Thu, 26 May 2011 02:48:54 -0000 On 5/25/2011 12:07 PM, Daniel Gerzo wrote: > I can only confirm this behavior. I have already reported this to > Mikolaj and we are trying to hunt down the problem. I have started > observing suddenly after some update. Unfortunately I haven't noted > which revision I started to observe this bug ;( > > Do you happen to use some net.inet sysctls/tunables? Not really. The only sysctls we override are UDP ones: net.inet.udp.blackhole=1 # --SSP-- net.inet.udp.recvspace=332800 # --SSP-- net.inet.udp.maxdgram=57344 # --SSP-- net.link.ether.inet.log_arp_wrong_iface=0 # - But at least it is good to know that we are not alone with this issue. -Maxim