From owner-freebsd-current@FreeBSD.ORG Mon Sep 22 16:47:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E0B16A4B3; Mon, 22 Sep 2003 16:47:51 -0700 (PDT) Received: from gw.fosburgh.org (user-0cetsgd.cable.mindspring.com [24.238.242.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B90B43FE9; Mon, 22 Sep 2003 16:47:48 -0700 (PDT) (envelope-from wotan@fosburgh.org) Received: by gw.fosburgh.org (Postfix, from userid 1001) id 436EDA80D; Mon, 22 Sep 2003 18:48:16 -0500 (CDT) From: Jonathan E Fosburgh To: Andreas Klemm , FreeBSD Current Date: Mon, 22 Sep 2003 18:48:14 -0500 User-Agent: KMail/1.5.2 References: <1064253832.19024.48.camel@tchoubou.scientiae.net> <20030922212857.GA23087@titan.klemm.apsfilter.org> In-Reply-To: <20030922212857.GA23087@titan.klemm.apsfilter.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309221848.15150.jonathan@fosburgh.org> Subject: Re: panic: lockmgr: locking against myself (current of 09-20th) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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 Sep 2003 23:47:51 -0000 On Monday 22 September 2003 04:28 pm, Andreas Klemm wrote: > The panic here is: > > (kgdb) symbol-file kernel.debug > Reading symbols from kernel.debug...done. > (kgdb) core-file /var/crash/vmcore.0 > No kernel exec file specified > (kgdb) exec-file kernel > (kgdb) core-file /var/crash/vmcore.0 > panic: lockmgr: locking against myself > panic messages: > --- > panic: lockmgr: locking against myself > panic: from debugger > Uptime: 10m26s > Dumping 191 MB > 16 32 48 64 80 96 112 128 144 160 176 I had a similar panic on 5.0-R. Do you happen to have any snapshots on any of the filesystems to which you might be writing at the time of the panic? I don't know how I determined it, but I found that the panic was the result of a snapshot on my /var filesystem. Removing the snapshot solved the panic. -- Jonathan Fosburgh AIX/SAN Administrator UT MD Anderson Cancer Center Houston, TX Home Page: http://www.fosburgh.org