(In reply to Michael from comment #83)
> The "WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state"
> doesn't flood the log file. The message appear only if the device is
> disconnected (after xhci died):
>
Could you take full logs and traces of this:
mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
< Trigger the issue >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace
In Bernhards case there were issues both with hardware not starting the
ring after soft retry, and software not handling context state error when stopping an endpoint. Second issue can be fixed in driver.
(In reply to Michael from comment #83)
> The "WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state"
> doesn't flood the log file. The message appear only if the device is
> disconnected (after xhci died):
>
Could you take full logs and traces of this:
mount -t debugfs none /sys/kernel/debug debug/dynamic_ debug/control debug/dynamic_ debug/control debug/tracing/ buffer_ size_kb debug/tracing/ events/ xhci-hcd/ enable debug/tracing/ trace
echo 'module xhci_hcd =p' >/sys/kernel/
echo 'module usbcore =p' >/sys/kernel/
echo 81920 > /sys/kernel/
echo 1 > /sys/kernel/
< Trigger the issue >
Send output of dmesg
Send content of /sys/kernel/
In Bernhards case there were issues both with hardware not starting the
ring after soft retry, and software not handling context state error when stopping an endpoint. Second issue can be fixed in driver.