From owner-freebsd-current@FreeBSD.ORG  Mon Jul 19 17:23:17 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0848516A4CE; Mon, 19 Jul 2004 17:23:17 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F11B843D46; Mon, 19 Jul 2004 17:23:16 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id E345572DF4; Mon, 19 Jul 2004 10:23:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id E058A72DF2; Mon, 19 Jul 2004 10:23:16 -0700 (PDT)
Date: Mon, 19 Jul 2004 10:23:16 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
In-Reply-To: <20040719145745.GH57678@darkness.comp.waw.pl>
Message-ID: <20040719102139.N59702@carver.gumbysoft.com>
References: <20040719145745.GH57678@darkness.comp.waw.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Unloading USB driver while device is attached.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2004 17:23:17 -0000

On Mon, 19 Jul 2004, Pawel Jakub Dawidek wrote:

> Hello.
>
> Could someone investigate what's going on for the situation from the
> subject? This panic is trivial to reproduce:
>
> 	# kldload umass.ko
> 	<plug in your USB bar>
> 	# kldunload umass
> 	# kldload umass
> 	<panic>
>
> It is not umass related! I think this problem is in our USB implementation.

Theres a discussion going on in -arch about making kldunload a bit more
careful about cleaning up before detaching.  In the interim adding a
method that just vetos any unload request would prevent this from
occuring, but also preclude unloading the driver. :)

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org