From owner-freebsd-current@FreeBSD.ORG Mon Aug 22 06:43:40 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 1EBDF1065687 for ; Mon, 22 Aug 2011 06:43:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 337458FC12 for ; Mon, 22 Aug 2011 06:43:38 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA01668; Mon, 22 Aug 2011 09:43:36 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QvOES-0003rU-D5; Mon, 22 Aug 2011 09:43:36 +0300 Message-ID: <4E51FA96.8090106@FreeBSD.org> Date: Mon, 22 Aug 2011 09:43:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110819 Thunderbird/6.0 MIME-Version: 1.0 To: Garrett Cooper References: In-Reply-To: X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , "Kenneth D. Merry" Subject: Re: panic: mtx_lock_spin: recursed on non-recursive mutex cnputs_mtx @ /usr/src/sys/kern/kern_cons.c:420 when running dump in ddb 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: Mon, 22 Aug 2011 06:43:40 -0000 on 22/08/2011 04:34 Garrett Cooper said the following: > On Thu, Aug 18, 2011 at 5:55 PM, Garrett Cooper wrote: >> Hi, >> Long story short, I was running a UP kernel on a netbook trying to >> stimulate a crash and when I did dump, it would periodically fail >> non-recursive mutex failure with the output shown below (I caught it >> once, but the other times the dump failed). > > This actually shows up when generating a panic via boot -v with > WITNESS, so it's potentially a race condition on my laptop. Adding > MTX_RECURSE to the mutex object didn't help things either. You may want to try to reproduce this panic with the following patch: http://article.gmane.org/gmane.os.freebsd.stable/76534 -- Andriy Gapon