On Thu, Aug 27, 2015 at 12:26:28AM +0200, Steinar H. Gunderson wrote: > However, at the same time I get these in dmesg: > > [ 221.350440] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted > [ 221.350559] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted > [ 221.350682] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted > [ 221.351402] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted > > They seem to come at the same time as my transfer errors, and I can't find > any documentation on them. Is this some sort of bug? I looked up the xHCI spec, and it seems to be something related to power saving (COMP_PING_ERR). So I compiled a kernel with CONFIG_PM=n, and lo and behold, the errors went away. I still don't have 100% stable recording (I seem to drop some blocks every now and then), but at least it's a step forward. I've noticed (with the CONFIG_PM=y kernel) that sometimes this comes up when inserting the device: [ 136.370917] usb 3-2: Set SEL for device-initiated U2 failed. I don't know if it's relevant. /* Steinar */ -- Homepage: http://www.sesse.net/ -- 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
