From owner-freebsd-stable@FreeBSD.ORG  Tue Jul 15 13:38:47 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5E3D637B401; Tue, 15 Jul 2003 13:38:47 -0700 (PDT)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 179EB43F75; Tue, 15 Jul 2003 13:38:46 -0700 (PDT)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h6FKch4D014793;
	Wed, 16 Jul 2003 00:38:44 +0400 (MSD)
	(envelope-from marck@rinet.ru)
Date: Wed, 16 Jul 2003 00:38:43 +0400 (MSD)
From: Dmitry Morozovsky <marck@rinet.ru>
To: Josef Karthauser <joe@FreeBSD.org>
In-Reply-To: <20030715203022.GB39304@genius.tao.org.uk>
Message-ID: <20030716003635.A14743@woozle.rinet.ru>
References: <20030712204434.Y74361@woozle.rinet.ru>
	<20030715203022.GB39304@genius.tao.org.uk>
X-NCC-RegID: ru.rinet
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: stable@FreeBSD.org
Subject: Re: usb.ko is unloadable?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2003 20:38:47 -0000

On Tue, 15 Jul 2003, Josef Karthauser wrote:

JK> > I'm planning to debug usb connection with my new SONY CLIE handheld, and found
JK> > that this process is much complicated by the fact usb.ko module can not be
JK> > unloaded 'cause some process is referencing it:

[snip]

JK> The usb module won't unload intentionally because we're not convinced
JK> that it correctly give back all allocated memory.  Take a look at the
JK> unload code in the driver source for confirmation.

Uh-oh. ;-)
Well, time to get into the way that uptime less than 100 days is not unusual
;-)

Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------