From owner-freebsd-hackers Mon Sep 13 16:59:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jules.res.cmu.edu (JULES.RES.CMU.EDU [128.2.144.56]) by hub.freebsd.org (Postfix) with ESMTP id C47AF14E8C for ; Mon, 13 Sep 1999 16:59:47 -0700 (PDT) (envelope-from greg@jules.res.cmu.edu) Received: from jules.res.cmu.edu (localhost [127.0.0.1]) by jules.res.cmu.edu (8.9.3/8.9.2) with ESMTP id UAA11296 for ; Mon, 13 Sep 1999 20:00:02 GMT (envelope-from greg@jules.res.cmu.edu) Message-Id: <199909132000.UAA11296@jules.res.cmu.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: debugging a proc's kernel stack... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Sep 1999 20:00:02 +0000 From: greg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I want to see where some a deadlock is occurring in the kernel. I've got a dump with a bunch of processes in the inode or namecache state. Can anybody give me a hint about how to find a proc's "kernel stack" - so that I can find out what these kernel was doing for these processes when it locked up... (see "repeated deadlocks in FS ..." on the smp list for more info about the problem)... thanks alot, greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message