I'm running an USB interrupt transfer with 2.4.22. It works fine until I unlink it. The reason is that the dev entry in the urb is zero. Unlink simply returns an error -19. If I force urb->dev to the dev I got from probe I get an -EINVAL. So the transfer loops forever and only a reboot can stop it.
(Of course) I'm not sure that I don't have any bugs in my driver. But also an unlink(urb) in the completion handler returns with the same error. The call of the unlink in the completion handler is only an emergency measure. Usually this should not happen. But the unlink from other parts of the driver also fails. Thus, unlink in both the completion handler and my standard termination function fails.
Any ideas?
/Bernd
-- Contact information: http://www.cn.stir.ac.uk/~bp1/
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
