From owner-freebsd-current Fri Feb 8 20:18:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id CDCDD37B419 for ; Fri, 8 Feb 2002 20:18:34 -0800 (PST) Received: (qmail 17991 invoked from network); 9 Feb 2002 04:18:33 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.153.230]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 04:18:33 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020208170756.B265@alicia.nttmcl.com> 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 , Julian Elischer 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