Date: Fri, 08 Feb 2002 23:18:30 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: "Eugene M. Kim" <gene@nttmcl.com> Cc: current@FreeBSD.ORG, David Wolfskill <david@catwhisker.org>, Julian Elischer <julian@elischer.org> Subject: Re: Hang on flushing buffers w/today's -CURRENT, SMP system Message-ID: <XFMail.020208231830.jhb@FreeBSD.org> In-Reply-To: <20020208170756.B265@alicia.nttmcl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <pid> 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 <jhb@FreeBSD.org> <>< 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.020208231830.jhb>