On 25.03.2018 14:31, Juho Tykkälä wrote:
Hello, Similar panic occurs on manually compiled 4.14.0. However, same issue occurs like bellow on 4.9.82 (debian compiled with package linux-image-4.9.0-6-amd64) One failure behavior: [70684.574901] xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint slot 12 ep 17 [70684.574914] xhci_hcd 0000:00:14.0: @0000000449d69a30 49fbd350 00400004 01000000 0cd28001 [70684.575860] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 11 comp_code 1 [70684.575875] xhci_hcd 0000:00:14.0: Looking for event-dma 0000000449fbd360 trb-start 0000000449fbd350 trb-end 0000000449fbd350 seg-start 0000000449fbd000 seg-end 0000000449fbdff0 Another failure behavior: [ 6880.362440] do_IRQ: 2.192 No irq handler for vector [ 6898.818312] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command. [ 6898.818334] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead [ 6898.818377] xhci_hcd 0000:00:14.0: HC died; cleaning up [ 6898.821178] usb 1-1: USB disconnect, device number 4 [ 6898.821279] usb 2-3: USB disconnect, device number 2 [ 6898.886250] usb 1-3: USB disconnect, device number 2 [ 6898.886377] usb 1-4: USB disconnect, device number 3 I believe the origin of the issue in hand is the same as in earlier panicing. Machine is the same and interval of the occurence is similar. The good thing is no panic with this kernel. The bad thing is no thunderbolt access control with this kernel.
Could you enable xhci traces with 4.14 or later, and send me the output: mount -t debugfs none /sys/kernel/debug echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable Then send me the /sys/kernel/debug/tracing/trace file after issue is triggered If it has been tracing for hours without triggering, the trace could be cleared every now and then with: echo 0 > /sys/kernel/debug/tracing/trace -Mathias -- 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
