> You've got it backward. The disconnect isn't _caused_ by the interrupt > URB; rather, the interrupt URB _reports_ the disconnect to the kernel. > In other words, the disconnect occurs first and then the interrupt URB > completes. Then I guess the traces aren't the right way to investigate the issue, because they report on the effects and not on the cause. What can constitute a disconnect if there is no signalling from the device? Device/hub power-cycles the link? What other troubleshooting options do I have? Is there more debugging output that I can enable? Will it help to raise a formal bug? Or did I do it already? :) Thanks Eugen -- 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
