On Sat, 1 Dec 2012, Udo van den Heuvel wrote: > > Secondly, try building a kernel with the patch below and > > CONFIG_USB_DEBUG enabled. Let's see what the dmesg log says when the > > problem occurs. > [root@a mesa]# dmesg|sort|uniq The sort messes up the order of the messages. uniq by itself would be okay, though. It would help if you also turn on CONFIG_PRINTK_TIME. These lines looks significant: > ohci_hcd 0000:00:13.0: IRQ: 44 8000001a > ohci_hcd 0000:00:13.0: IRQ: 4 8000001a > ohci_hcd 0000:00:13.0: IRQ: 4 8000005a > ohci_hcd 0000:00:13.0: IRQ: 64 5a The last one is strange. I wouldn't expect it to appear, because 0x64 & 0x5a = 0x40 is nonzero. But it's had to say much without knowing where this message belongs in the log. > I had to hurry as the debug patch overflows dmesg very quickly. > That is the reason why the dmesg is sorted and uniq'd etc. > I do hope there is enough info to further this issue. No, not really. The patch could be modified to reduce the amount of output, if you think that would help. 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
