From owner-freebsd-bugs@freebsd.org  Wed Dec  2 15:29:35 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 00C05A3E285
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed,  2 Dec 2015 15:29:34 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D97D8151D
 for <freebsd-bugs@FreeBSD.org>; Wed,  2 Dec 2015 15:29:34 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tB2FTYbh069500
 for <freebsd-bugs@FreeBSD.org>; Wed, 2 Dec 2015 15:29:34 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 204949] panic: mtx_lock of spin mutex @
 /usr/src/head/sys/kern/vfs_subr.c:512
Date: Wed, 02 Dec 2015 15:29:35 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-204949-8-WgRhU9PHsJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204949-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-204949-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2015 15:29:35 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204949

--- Comment #6 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Jason Unovitch from comment #5)
What does 'M' mean in your kernel revision ? What changes did you apply ?

>From the core at the reference above, in kgdb do 'frame 12\nprint *mp' and post
the result.

There were some changes to the vnode handling in the timeframe of recent two
weeks, but your problem is about the state of the struct mount, and not vnode.

-- 
You are receiving this mail because:
You are the assignee for the bug.