Unloading USB driver while device is attached.

[Pawel Jakub Dawidek]

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.

-- 
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd at FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040719/3df83f0b/attachment.bin