Hello, I am trying to help somebody fix this longtime bug in xhci_hcd driver. (or more likely bug in ASMedia controller that we co I will try provide as much information as I can. My setup: I am using USB TV tuner card connected to ASMedia USB 3.1 port on mainboard. 00:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation ASM1142 USB 3.1 Host Controller Flags: bus master, fast devsel, latency 0, IRQ 34, NUMA node 0 Memory at df200000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [68] MSI-X: Enable+ Count=8 Masked- Capabilities: [78] Power Management version 3 Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [280] #19 Capabilities: [300] Latency Tolerance Reporting Kernel driver in use: xhci_hcd Kernel modules: xhci_pci Device is 1b21:1242 Sometimes after few hours, sometimes after 1-2 days - the xhci_hcd driver crash with similar error in dmesg: [125235.391809] xhci_hcd 0000:00:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 3 [125235.391843] xhci_hcd 0000:00:00.0: Looking for event-dma 000000021231a690 trb-start 000000021231a890 trb-end 000000021231a8b0 seg-start 000000021231a000 seg-end 000000021231aff0 It never happens if I connect my USB TV tuner card to the onboard Intel USB 3.0 ports. Only with ASMedia USB 3.1 port. There same issue is present at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 but for different ASMedia controller. I have logs: mount -t debugfs none /sys/kernel/debug echo xhci-hcd >> /sys/kernel/debug/tracing/set_event cat /sys/kernel/debug/tracing/trace But people from launchpad told me they are not applicable. Please help me to provide the necessary information to fix this issue. Thanks -- 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
