From owner-freebsd-current@FreeBSD.ORG Mon Aug 22 01:34:24 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 619D2106566C; Mon, 22 Aug 2011 01:34:24 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id F1BB28FC0C; Mon, 22 Aug 2011 01:34:23 +0000 (UTC) Received: by qwc9 with SMTP id 9so3671794qwc.13 for ; Sun, 21 Aug 2011 18:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=wfllWerNDr+DMVuCu4M7AXF+ExZj64nb/3QLzbH7KE8=; b=dQaOalI359uv41U+qRZ001tRGLH1fgUmu/toPJO3oTneKLYHLyJoZxBWGACSwx/91E usxZvRseeITIA2cm2zuTk3Y8yCNY48rFS1jMLYQ6xJvWciE03+4q+ccGZhzXyeHc9vNR niW4ikLIugMiZsRuZ5QXxf6ywNXOyKJjalfks= MIME-Version: 1.0 Received: by 10.224.218.193 with SMTP id hr1mr1133198qab.29.1313976863294; Sun, 21 Aug 2011 18:34:23 -0700 (PDT) Received: by 10.224.178.65 with HTTP; Sun, 21 Aug 2011 18:34:23 -0700 (PDT) In-Reply-To: References: Date: Sun, 21 Aug 2011 18:34:23 -0700 Message-ID: From: Garrett Cooper To: Andriy Gapon , "Kenneth D. Merry" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current 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 01:34:24 -0000 On Thu, Aug 18, 2011 at 5:55 PM, Garrett Cooper wrote: > Hi, > =A0 =A0Long 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. Thanks, -Garrett