Hi, It seems that under some conditions when a usb device is physically disconnected and there are some pending urbs ehci_endpoint_disable can loop forever in state QH_STATE_UNLINK. I can't really see whether this can be a hardware problem or it is purely in software as I don't understand the mechanisms involved. Can anyone suggest a debugging technique? This happens with a clean 2.6.10 kernel. This is triggered by my user space driver calling usb_release_interface when it detects a disconnect by a read or write to the device failing.
/Brian ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
