Re: USB deadlock after resume
Oliver Neukum <[email protected]>
| Newsgroups | gmane.linux.usb.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
Am Mittwoch 21 November 2007 schrieb Felipe Balbi: > Hi, > > On Wed, 21 Nov 2007 15:37:20 +0100, "Markus Rechberger" > <[email protected]> wrote: > > it's the usb_control_message which calls usb_kill_urb if I haven't got > > it wrong. (if you're looking for some other information please let me > > know) > > Although, I got a bit further with it. The error seems to happen > > earlier already. > > If I load the driver, and do not access the device after suspending > > all usb_control commands fail with -71 eproto. > > This device shouldn't be suspended. AFAIK it should have auto_suspend > disabled > by default. > > Try adding this device to drivers/usb/core/quirks.c with > USB_QUIRK_NO_AUTOSUSPEND flag set. Something like: Unless the device sets a flag it won't be autosuspended. Nevertheless it will and must be suspended as the whole system is supended. Regards Oliver ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel