From owner-freebsd-arch@FreeBSD.ORG  Wed Jul 21 06:44:37 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 00D5516A4CE; Wed, 21 Jul 2004 06:44:37 +0000 (GMT)
Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [195.41.46.235])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4BEC343D5C; Wed, 21 Jul 2004 06:44:36 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (0x50a07c53.naenxx7.adsl-dhcp.tele.dk
	[80.160.124.83])
	by pfepa.post.tele.dk (Postfix) with ESMTP id 4296A47FE09;
	Wed, 21 Jul 2004 08:44:34 +0200 (CEST)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6L6iXTd077807;
	Wed, 21 Jul 2004 08:44:33 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: David Schultz <das@FreeBSD.ORG>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 20 Jul 2004 13:37:39 PDT."
             <20040720203739.GA72252@VARK.homeunix.com> 
Date: Wed, 21 Jul 2004 08:44:33 +0200
Message-ID: <77806.1090392273@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: Brian Fundakowski Feldman <green@FreeBSD.ORG>
cc: arch@FreeBSD.ORG
Subject: Re: kldunload DIAGNOSTIC idea... 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2004 06:44:37 -0000

In message <20040720203739.GA72252@VARK.homeunix.com>, David Schultz writes:

>> Looking for sleep addresses inside the module might make sense too.
>
>But this is just a heuristic that may sometimes fail.  The module
>might be holding resources or locks, it could have callbacks, etc.
>If we're going to offer a forcible unload option, [...]

This has _nothing_ to do with forcible unload.

Please read the subject, again if necessary.

This is an idea for a debug tool which may help people properly
debug and implement unload *in general*.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.