On 20.12.2019 15.50, Rene D. Obermueller wrote:
Hello, I'm trying to connect a USB audio device (DJ-Tech CTRL) to my laptop using a Linux 5.4.5 kernel (with Debian patches, but not for xhci), but that fails with the above error message. I've tried with a number of kernels before during the last 9 months with the same result, but didn't get round to actually collect the debug log and make a bug report yet. The device worked on two different computers (one Windows 10, the other an older 4.x Linux kernel) that have USB2 ports. I've attached dynamic debug output (module xhci_hcd =pflm) from a connection attempt. Is there any other info I should provide or any other tests (vanilla kernel, rc kernel or the like) I should perform?
0x11 is Parameter error "Asserted by a command if a Context parameter is invalid." adding xhci tracing will show more details. 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 < plug in USB audio device, let it fail > Send content of /sys/kernel/debug/tracing/trace Your log shows it's related to the input context pointed to when we issue a configure endpoint command: [ 5063.518821] usb 3-2.3: New USB device found, idVendor=2485, idProduct=504f, bcdDevice= 2.54 [ 5063.518825] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5063.518828] usb 3-2.3: Product: CTRL [ 5063.518830] usb 3-2.3: Manufacturer: CTRL [ 5063.518832] usb 3-2.3: SerialNumber: CTRL [ 5063.519100] xhci_hcd:xhci_add_endpoint:1917: xhci_hcd 0000:05:00.4: add ep 0x1, slot id 9, new drop flags = 0x0, new add flags = 0x5 [ 5063.519113] xhci_hcd:xhci_add_endpoint:1917: xhci_hcd 0000:05:00.4: add ep 0x81, slot id 9, new drop flags = 0x0, new add flags = 0xd [ 5063.519118] xhci_hcd:xhci_check_bandwidth:2878: xhci_hcd 0000:05:00.4: xhci_check_bandwidth called for udev 00000000f9c39172 [ 5063.519123] xhci_hcd:xhci_ring_cmd_db:282: xhci_hcd 0000:05:00.4: // Ding dong! [ 5063.519167] xhci_hcd 0000:05:00.4: ERROR: unexpected command completion code 0x11. Could be any part of the input context. (input control context, slot context, or one of the endpoint context). xhci tracepoints will show the input control context and the slot context. If those seem fine we might need to add a hack that just dumps everything, including all endpoint contexts -Mathias
