From owner-freebsd-current@FreeBSD.ORG Wed Jan 16 09:55:49 2008 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 51FC216A41B for ; Wed, 16 Jan 2008 09:55:49 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8F77713C459; Wed, 16 Jan 2008 09:55:47 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <478DD4A2.6020202@FreeBSD.org> Date: Wed, 16 Jan 2008 10:55:46 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Scot Hetzel References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <790a9fff0801152301l5d50461aw3a253608506368e2@mail.gmail.com> In-Reply-To: <790a9fff0801152301l5d50461aw3a253608506368e2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2008 09:55:49 -0000 Scot Hetzel wrote: > On 1/15/08, Kostik Belousov wrote: >> On Tue, Jan 15, 2008 at 07:52:12AM -0600, Scot Hetzel wrote: >>> When I boot a Jan 13th or Jan 15th kernel, and then run >>> /usr/local/etc/cvsup/update.sh to update the local CVS repository, I >>> get the following panic: >>> >>> panic: System call lstat returning with 1 locks held >>> cpuid = 0 >>> KDB: enter: panic >>> [thread ; pid 1240 tid 10031] >>> stopped at kdb_enter+0x3d: movq $0,0x41b048(%rip) >>> db> show alllocks >>> db> show locks >>> db> bt >>> tracing pid 1240 tid 10031 td 0xffffff001c1ad360 >>> kdb_enter() at kdb_enter+0x3d >>> panic() at panic+0x176 >>> syscalls() at syscalls+0x66d >>> Xfast_syscalls() at Xfast_syscalls+0xab >>> --- syscall (0, FreeBSD ELF64, nosys), rip = 0x8009e87ec, rsp= >>> 0x72ec50, rbp = 0x72ed28 --- >>> >> 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 added DEBUG_VFS_LOCKS to the kernel config file, rebuilt and > installed the kernel. After rebooting the system, I started the cvsup > update for my local mirror, when the panic occured I received a > similar panic to the one above. When I used 'show lockedvnods' the > only thing that was displayed was 'Locked vnodes' and that was it. > > I'm going to try a binary search to see if I can narrow the problem down. Do you also have witness enabled? Kris