On Sunday 24 April 2005 2:26 pm, Alan Stern wrote: > ... > > At this point there was a normal "device suspended" debugging message, > followed by a message that the root hub was suspending. However both > power/state and *0/power/state contained 0, so as far as usbcore was > concerned neither the root hub device nor its driver was suspended.
The sysfs state _should_ be irrelevant. In practice, the sticking point has been the root hub timer. Paths that affect the sysfs power/state file were also -- last I looked -- the ones that would disable or enable the root hub timer. > Then I unplugged the device. This caused a complete system lockup. > Further testing showed that the (ints & OHCI_INTR_RD) case in ohci_irq() > was being executed over and over again. Apparently the interrupt source > was not getting cleared properly. > > This is very reminiscent of the problem you found with the original > version of the root-hub-IRQ patch. Is it correct to assume that both > problems will be fixed by the same change to the driver? The failure mode is reminiscent, but I've never seen that happen with INTR_RD before. The OHCI spec says INTR_RD happens along with transitioning to OHCI_USB_RESUME. What did you change to make the hardware do that transition more than once? - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
