On Tue, 19 Apr 2011, Paul Stewart wrote: > Set a flag if the interrupt URB completes with ENOENT as this > occurs legitimately during system suspend. When the usbnet_bh > is called after resume, test this flag and try once to resubmit > the interrupt URB. No doubt there's a good reason for doing things this way, but it isn't clear. Why wait until usbnet_bh() is called after resume? Why not resubmit the interrupt URB _during_ usbnet_resume()? This would seem to be the logical approach, seeing as how usbnet_suspend() kills the interrupt URB. For that matter, where does the interrupt URB get deallocated? It obviously gets allocated in init_status(), but it doesn't seem to be freed anywhere. Alan Stern -- 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
