From owner-freebsd-current@FreeBSD.ORG  Thu Jan 24 12:28:08 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 56AB116A41A;
	Thu, 24 Jan 2008 12:28:08 +0000 (UTC) (envelope-from yar@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 45C8C13C46B;
	Thu, 24 Jan 2008 12:28:08 +0000 (UTC) (envelope-from yar@FreeBSD.org)
Received: from freefall.freebsd.org (yar@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0OCS8Eh038947;
	Thu, 24 Jan 2008 12:28:08 GMT
	(envelope-from yar@freefall.freebsd.org)
Received: (from yar@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0OCS8fN038946;
	Thu, 24 Jan 2008 12:28:08 GMT (envelope-from yar)
Date: Thu, 24 Jan 2008 12:28:08 +0000
From: Yar Tikhiy <yar@FreeBSD.org>
To: Kostik Belousov <kostikbel@gmail.com>
Message-ID: <20080124122808.GA15600@freefall.freebsd.org>
References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com>
	<20080115143924.GB57756@deviant.kiev.zoral.com.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080115143924.GB57756@deviant.kiev.zoral.com.ua>
User-Agent: Mutt/1.4.2.3i
Cc: Attilio Rao <attilio@FreeBSD.org>, freebsd-current@FreeBSD.org
Subject: Re: panic: System call lstat returning with 1 locks held
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2008 12:28:08 -0000

On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote:
>
> I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes.
> Please, add DEBUG_VFS_LOCKS to the kernel config, and do the
> 	show lockedvnods
> from the ddb prompt when the panic occurs. The witness does not track
> the lockmgr locks.

I think I'm seeing the same panic on UFS.  It's rather nasty: I
cannot rebuild CURRENT natively due to it so I have to build it
under 6-STABLE.  My favourite way to trigger the panic reliably is
running `make install' in a simple port directory, e.g., portmaster,
but my system also panics during daily scripts run and, as already
said, if trying to build world.

Now my kernel config is:

	include GENERIC
	ident	"_LOCKTEST"
	options DEBUG_VFS_LOCKS

Attached is the debug output after the panic.  Alas, no locked
vnodes are shown.  How can I help to investigate this issue
further?

Yar

panic: System call lstat returning with 1 locks held
cpuid = 0
KDB: enter: panic
[thread pid 2024 tid 100102 ]
Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
db> show lockedvnods
Locked vnodes
db> where
Tracing pid 2024 tid 100102 td 0xc3720000
kdb_enter(c0b0bdc0,c0b0bdc0,c0b3c319,d6218c8c,0,...) at kdb_enter+0x3a
panic(c0b3c319,c0b11902,1,c0b11902,c0bbf390,...) at panic+0x12c
syscall(d6218d38) at syscall+0x46e
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (0, FreeBSD ELF32, nosys), eip = 0x2815da8b, esp = 0xbfbfe86c, ebp = 0xbfbfe8f8 ---