From owner-freebsd-current@FreeBSD.ORG Sat Aug 10 21:29:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 26FD9D93 for ; Sat, 10 Aug 2013 21:29:35 +0000 (UTC) (envelope-from bryan-lists@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B69AD21E9 for ; Sat, 10 Aug 2013 21:29:34 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sweb; b=FoIPG6 i2jt5EAuZEzZifuV3KoUx2NB6K6z2TCapPS9sNoexG4CSVHlJctiRvYeH5uiexqJ xtX1N+7xqOyGE/HChP+GM56xUYMH2cNzIgMUNXLxHVYG/tH5AngAoiXAkF6NEw8U ypYXG9A7xGo/BZWwJpzon/e+Llsfl3FOqnmpU= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sweb; bh=FhaqJR552LVf 7roTzAUnXO5YiT4keas8190X7t5PS3M=; b=ER3CZtK6l9cZ8OUhMHJbyDcSGQkq gCSitzkwQjvnsIWGqTj6kULdwVUpDD6v8tFAc+ybtPQ9fxwAaAmvEmq4G47z7t5T AhzUmX4xfMBxFnoz4pjOeRe/6JRlcTIxG2Jn5XMwSPhSgcFmQzcwHv46DtxhI7DX n2k5mu43FZZXkyw= Received: (qmail 30702 invoked from network); 10 Aug 2013 16:29:32 -0500 Received: from unknown (HELO ?10.10.0.24?) (bryan@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 10 Aug 2013 16:29:32 -0500 Message-ID: <5206B0B0.7030201@shatow.net> Date: Sat, 10 Aug 2013 16:29:20 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: panic on boot with fresh current References: <20130810112410.GA27286@devbox.vnode.local> <52066DE0.2060305@shatow.net> <52067537.2070309@shatow.net> <20130810174407.GD4972@kib.kiev.ua> <20130810174547.GE4972@kib.kiev.ua> <20130810182109.GG4972@kib.kiev.ua> In-Reply-To: <20130810182109.GG4972@kib.kiev.ua> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 10 Aug 2013 21:29:35 -0000 On 8/10/2013 1:21 PM, Konstantin Belousov wrote: > On Sat, Aug 10, 2013 at 08:45:47PM +0300, Konstantin Belousov wrote: >> On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote: >>> On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: >>>> On 8/10/2013 11:44 AM, Bryan Drewery wrote: >>>>> On 8/10/2013 6:24 AM, Joel Dahl wrote: >>>>>> panic: witness_init: pending locks list is too small, increase >>>>>> WITNESS_PENDLIST >>>>> I also get this. The last stable revision for me was r254150 >>>> >>>> r254150 stable, r254171 panic. >>>> >>>> backtrace: https://dl.dropboxusercontent.com/u/8732004/r254171-panic.jpg >>> >>> So could you point to exact commit which causes panic ? >> It is r254167, right ? >> > So I cannot reproduce it locally. The problem is that r254167 moved sleepq > initialization before witness is operational, and witness has a backlog > of locks initialized before witness init. The backlog overflown. > > The right fix looks to be just what the panic message told, please try > this: Yup this patch fixed it, as stated. Thank you for looking at this. -- Regards, Bryan Drewery