From owner-freebsd-current Mon Feb 11 19:26:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 79C7A37B49F for ; Mon, 11 Feb 2002 18:18:18 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 783002333C; Mon, 11 Feb 2002 21:17:28 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 529B69F33A; Mon, 11 Feb 2002 21:12:22 -0500 (EST) Date: Fri, 08 Feb 2002 23:18:30 -0500 (EST) From: John Baldwin To: "Eugene M. Kim" Subject: Re: Hang on flushing buffers w/today's -CURRENT, SMP system Cc: current@FreeBSD.ORG, David Wolfskill , Message-Id: <20020212021222.529B69F33A@okeeffe.bestweb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 09-Feb-02 Eugene M. Kim wrote: > I'm not particularly good at reading the lock-related output, but it > doesn't have other lines than the one that says about the Giant lock, so > it seems there isn't any other locks being held by anyone. show locks only shows the locks held by a single thread. Trying to show all locks in the system would be a bit more work. You would basically need to add a new DDB command that walked the allproc list doing a show locks on each thread. show witness really isn't useful in most cases unless you are working on witness itself. It merely shows the tree of lock order relationships. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message