On Mon, Aug 31, 2015 at 05:28:10PM +0300, Mathias Nyman wrote: > The "ERROR Transfer event TRB DMA ptr not part of curren..." errors are a bit worrying. > I was hoping these would no longer occur after the last off by one fix: > > commit 7895086afde2a05fa24a0e410d8e6b75ca7c8fdd > xhci: fix off by one error in TRB DMA address boundary check I'm still seeing both of these errors on 4.3-rc1: Sep 20 00:45:40 klump kernel: [89167.209335] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted Sep 20 00:45:40 klump kernel: [89167.209421] xhci_hcd 0000:00:14.0: ERROR Unknown event condition 20, HC probably busted Sep 20 00:45:40 klump kernel: [89167.209588] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 Sep 20 00:45:40 klump kernel: [89167.209600] xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fff87030 trb-start 00000000fff87000 trb-end 00000000fff87000 seg-start 00000000fff87000 seg-end 00000000fff87ff0 Sep 20 00:45:40 klump kernel: [89167.209717] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 Sep 20 00:45:40 klump kernel: [89167.209722] xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fff87040 trb-start 00000000fff87000 trb-end 00000000fff87000 seg-start 00000000fff87000 seg-end 00000000fff87ff0 Sep 20 00:45:40 klump kernel: [89167.209833] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 Sep 20 00:45:40 klump kernel: [89167.209836] xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fff87050 trb-start 00000000fff87000 trb-end 00000000fff87000 seg-start 00000000fff87000 seg-end 00000000fff87ff0 Sep 20 00:45:40 klump kernel: [89167.209957] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 Sep 20 00:45:40 klump kernel: [89167.209960] xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fff87060 trb-start 00000000fff87000 trb-end 00000000fff87000 seg-start 00000000fff87000 seg-end 00000000fff87ff0 The device doesn't like Linux' power saving in general, it seems; frequently, when I set a configuration (during initialization of the device, from libusb), this happens on the next call (setting the alternate): [94064.745001] usb 2-1: Enable of device-initiated U2 failed. [94065.113294] usb 2-1: USB disconnect, device number 49 No idea whether it's related. It's sure annoying, though :-) /* 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
