From owner-freebsd-hackers Mon Mar 27 8:48:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ra.nks.net (ra.nks.net [208.226.218.5]) by hub.freebsd.org (Postfix) with ESMTP id A87BF37BE7C for ; Mon, 27 Mar 2000 08:48:37 -0800 (PST) (envelope-from joeo@cracktown.com) Received: from localhost (joeo@localhost) by ra.nks.net (8.8.7/8.8.7) with ESMTP id LAA06856 for ; Mon, 27 Mar 2000 11:48:38 -0500 Date: Mon, 27 Mar 2000 11:48:38 -0500 (EST) From: X-Sender: joeo@ra.nks.net To: hackers@freebsd.org Subject: figuring out were an spl lock isn't being freed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm playing with a third party kernel module under 4.0. Occasionally the box locks up during extended access to the device it supports, though the box will respond to pings and other hardware driven interupts, but will not let loggins happen, and open telnet sessions from remote hosts freeze. I'm guessing an spltty isn't being freed. What's the best way to go about figuring out what function isn't freeing the lock or returning? Thanks for any help, Joe Orthoefer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message