From owner-freebsd-hackers@freebsd.org Wed Aug 10 23:13:29 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4324EBB5D61 for ; Wed, 10 Aug 2016 23:13:29 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C42D611DE for ; Wed, 10 Aug 2016 23:13:28 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id q128so121130469wma.1 for ; Wed, 10 Aug 2016 16:13:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to; bh=yRRqnDLqHjo/jgDCBJ3HS0xA1SW8N24DoKwWhYG2T8A=; b=YNNevA7jyMHxjvWse30Ac5rCl9EPKvzf6x+yk1Uu/MX8qOKplyl4TbDpknTKshSmkU D+TQDQ469ZY4sHuCNxChmvRDgFuJkAKR1lZS9VIldwsW6EZWyfVHuljNr8yxweROcfvD mjZMJyHNoqM5aQHUiF2krTO4QzjZ5SOJLX0+pm4XoawXlHE5TZj+2BRipsqp+oa2fyPA ErcVgnQymS25hjTwBcuQ96lGnlA0eQCq8bwBnimO7lqCiwB293T8KMAYp65cQ/MkLQMa mHcO+e4rY2e11EgWHx6Qd3IBb7jSxQjF0rez6CA34I9A8GrYkOtQ3TIw/F0Zg+LT4e/i YWNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to; bh=yRRqnDLqHjo/jgDCBJ3HS0xA1SW8N24DoKwWhYG2T8A=; b=GVZZxxwG2cEWAhheBlHEAcIJkoO25+8GGav00aKyABZd545BMrzoAX504qFHovixJB XUZMc1hPelcpqPFxBbaO+/RNWdYENnyKD3Vz6x9rna23rLzMDzURVHvigUhYy1vTbHnM LqkVfXqwOuxD21hjSJNO9oi4jsxxkX7s5YVxnPXX3RDEDKpidMtk3WlcJUgf0n2izHCr Z6LUgl33lH42jc3qez3vwHPeOEq8NzYZsNEXg3j5quvr6rhuB8IutBWGl085g5aUUjGH Ax0ZhYI7z0Wd7w55qkSv1ayur49kvCRMGIY8S2ipRTNXehXUn5BqPhnpRlZgt/zpQU3R fEJw== X-Gm-Message-State: AEkooutI0gqIqaRySZL0OwrUlPcRK/GgdLxubfwrBo8CeTWZonW+e8FyV08mUDiYLjWEFQ== X-Received: by 10.194.190.232 with SMTP id gt8mr6280705wjc.141.1470870805863; Wed, 10 Aug 2016 16:13:25 -0700 (PDT) Received: from [192.168.2.30] ([2.190.216.101]) by smtp.googlemail.com with ESMTPSA id cw7sm11347486wjb.38.2016.08.10.16.13.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Aug 2016 16:13:25 -0700 (PDT) Message-ID: <57ABB512.4030503@gmail.com> Date: Thu, 11 Aug 2016 03:43:22 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ryan Stone CC: Konstantin Belousov , FreeBSD Hackers Subject: Re: 9.3-RELEASE panic: spin lock held too long References: <57AB349B.2010805@gmail.com> <20160810141948.GP83214@kib.kiev.ua> <57AB462A.2080608@gmail.com> <57AB632D.4000501@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2016 23:13:29 -0000 On 2016-08-10 22:10, Ryan Stone wrote: > On Wed, Aug 10, 2016 at 1:23 PM, Hooman Fazaeli > wrote: > > No. I have panics involving 'turnstile lock' (see the original post) and 'sched lock 2' too. > > > That doesn't necessarily mean that the root cause isn't due to sched lock 0 being leaked. You'd have to dig into the cores and look at the chain of dependent locks to be sure. Give the patch a > try; it should panic quite quickly if it's the issue I am thinking of. Sure, I will. BTW, what do you exactly mean by lock leaking? Is there a list for the possible causes of 'spin lock held too long' panics? I mean, what sorts of coding bugs may cause a thread to hold a spin lock for a long time? Such a list would provide me an starting point for diagnostics. And, How much long is 'too long'? What is the justification behind the few million for() loop iterations that _mtx_lock_spin waits to grab a spin lock? Thanks. -- Best regards Hooman Fazaeli