Johannes Erdfelt <[EMAIL PROTECTED]> writes: >> Obviously I don't know if this is a controller issue or my driver >> issue. It could be some bug in the disconnect routine. I have an >> interrupt urb that I don't think I'm unlinking at disconnect time. > > While I can't guarantee that the patch I gave you wouldn't cause this, I > don't think it would. > > It sounds like this is a different bug.
Yea, when I unlinked my interrupt urb in the disconnect routine it cleared up. I did many disconnects and was unable to reproduce. Don't pretend to understand what happened, just glad it went away :) > BTW - Your driver probably shouldn't be incrementing the usage count > at connect time, only when an application opens the device. I'm incrementing usage count by side effect :(. I've implemented a ram-based driver fs similar to what Greg put in PCI Hotplug. The problem is that I've called kern_mount in my connection sequence. That is incrementing the usage count. I don't know how to get around this. The disconnect routine is the only place that I'm unmounting the driver fs. Is there some routine that I can know will get called at module unload time to insure my driver fs is unmounted? -- (__) Doug Alcorn - Unix/Linux/Web Developing oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ mailto:[EMAIL PROTECTED] http://www.lathi.net ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
