From owner-freebsd-current@FreeBSD.ORG  Mon Jul 19 14:57:47 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 7E5F616A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 19 Jul 2004 14:57:47 +0000 (GMT)
Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 30FC743D4C
	for <freebsd-current@freebsd.org>;
	Mon, 19 Jul 2004 14:57:47 +0000 (GMT)
	(envelope-from pjd@darkness.comp.waw.pl)
Received: by darkness.comp.waw.pl (Postfix, from userid 1009)
	id 95966ACAFB; Mon, 19 Jul 2004 16:57:45 +0200 (CEST)
Date: Mon, 19 Jul 2004 16:57:45 +0200
From: Pawel Jakub Dawidek <pjd@FreeBSD.org>
To: freebsd-current@freebsd.org
Message-ID: <20040719145745.GH57678@darkness.comp.waw.pl>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="3ecMC0kzqsE2ddMN"
Content-Disposition: inline
User-Agent: Mutt/1.4.2i
X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc
X-OS: FreeBSD 5.2.1-RC2 i386
Subject: 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 14:57:47 -0000


--3ecMC0kzqsE2ddMN
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.

One more note with could be helpful.
When device is already inserted and I load USB driver, <drvname>_match
isn't called, but when driver was unloaded while device was in and it is
loaded again (as in my example) <drvname>_match is called and we have
a problem, because there are some stale data, I think (not everything
is cleaned up on kldunload?).
Ok, one more note.
You can also set 'break <drvname>_match' in DDB and try to compare
backtraces when device is removed while driver is loaded and when you
unload USB driver.

--=20
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd@FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!

--3ecMC0kzqsE2ddMN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFA++FpForvXbEpPzQRAtk4AKCB8Y3dJ4lrK6DKCjyhl44nIftJJwCfaLSH
PgDklVxfMdW8o9OfFhj7DUM=
=ib6s
-----END PGP SIGNATURE-----

--3ecMC0kzqsE2ddMN--