Am Montag, 3. August 2009 16:46:39 schrieb Alex Riesen: > >> Cool. How can I help? > > > > You have to put printks in acm_disconnect to find out where it returns > > to early or if it is not called at all. > > I have hard time guessing exactly where to put them, without knowing > what in acm_disconnect modifies the data pointed by ->ep_in and ->ep_out. > My late impression was that acm_disconnect _is_ called. Impression? Secure knowledge would be better than an impression ;-) Anyway, there's no way acm_rx_tasklet should run at all, because acm_disconnect sets acm->dev to NULL which should make ACM_READY return 0 and thus cause acm_rx_tasklet to do nothing. You need to find out whether acm->dev is set to NULL, and if it isn't, why it isn't unset. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
