Re: testusb: epipe errors on test 9 and 10

[Greg KH <gregkh@linuxfoundation.org>]

On Thu, Nov 27, 2025 at 09:06:24AM +0100, Angelo Dureghello wrote:
> Hi all,
> 
> looking for some help on testusb tool tests 9,10 always failing with
> -EPIPE, kind of ep stall. Peripheral side has g_zero loaded.
> 
> Devices under test are custom boards, have same qualcomm 8 cores cpu, and
> kernel is android 5.4. Involved drivers in both devices are xhci and dwc3.
> Anyway, connection under tests is 2.0 microusb connector on both side.

5.4 is _very_ old and obsolete and odds are you are paying for support
for that kernel from a company if you are stuck with it (hint, it is
going to go end-of-life in 3 days).  Please contact them as you are
paying for this kind of thing from your vendor.

If you can reproduce this with the latest release (6.17), please let us
know.

> /dev/bus/usb/001/007 test 9 --> 5 (I/O error)
> /dev/bus/usb/001/007 test 10 --> 32 (Broken pipe)
> 
> usbmon shows for both cases some EPIPE:
> 
> ffffff85bf04b100 1951528285 S Ci:1:007:0 s 80 00 0000 0000 0002 2 <
> ffffff85bf04b100 1951528785 C Ci:1:007:0 0 2 = 0100
> ffffff85bf04b100 1951529102 S Ci:1:007:0 s 81 00 0000 0000 0002 2 <
> ffffff85bf04b100 1951529554 C Ci:1:007:0 -32 0   <== EPIPE
> /dev/bus/usb/001/007 test 9 --> 5 (I/O error)
> 
> ffffff85bb5b2100 3778244155 C Ci:1:007:0 0 18 = 12010002 ff000040 2505a0a4
> 04050102 0302
> ffffff85bb5b2100 3778244178 S Ci:1:007:0 s 80 06 0100 0000 0012 18 <
> ffffff85bb5b0100 3778245631 C Ci:1:007:0 0 9 = 09024500 010304c0 00
> ffffff85bb5b0100 3778245693 S Ci:1:007:0 s 80 06 0200 0000 0009 9 <
> ffffff85bb5b1500 3778247900 C Ci:1:007:0 0 1 = 00
> ffffff85bb5b1500 3778247964 S Ci:1:007:0 s 81 0a 0000 0000 0001 1 <
> ffffff85bb5b4100 3778249094 C Ci:1:007:0 -32 0    EPIPE
> ffffff85bb5b7100 3778249432 C Ci:1:007:0 -104 0   ECONNRESET
> ffffff85bb5b4500 3778249493 C Ci:1:007:0 -104 0
> ffffff85bb5b3500 3778249519 C Ci:1:007:0 -104 0
> ffffff85bb5b3900 3778249544 C Ci:1:007:0 -104 0
> ffffff85bb5b6500 3778249569 C Co:1:007:0 -104 0
> ffffff85bb5b6900 3778249602 C Ci:1:007:0 -104 0
> ffffff85c5b6e100 3778249631 C Ci:1:007:0 -104 0
> ffffff85c5b6ed00 3778249653 C Ci:1:007:0 -104 0
> ffffff85c5b6dd00 3778249674 C Ci:1:007:0 -104 0
> ffffff85c5b6d500 3778249697 C Ci:1:007:0 -104 0
> ffffff85c5b6b500 3778249727 C Ci:1:007:0 -104 0
> ffffff85c5b6fd00 3778249755 C Ci:1:007:0 -104 0
> ffffff85c5b6a900 3778249775 C Ci:1:007:0 -104 0
> ffffff85c5b6ad00 3778249795 C Ci:1:007:0 -104 0
> ffffff85c5b6b100 3778249815 C Ci:1:007:0 -104 0
> ffffff85c5b6c500 3778249844 C Ci:1:007:0 -104 0
> ffffff85c5b6d900 3778249869 C Ci:1:007:0 -104 0
> /dev/bus/usb/001/007 test 10 --> 32 (Broken pipe)

Any hints on logs from the device side as to what is happening?  Any
debug logs?  If this is an i/o error, the controller might be logging
something that went wrong.

thanks,

greg k-h