From: Greg KH <gregkh@linuxfoundation.org>
To: Angelo Dureghello <angelo@kernel-space.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: testusb: epipe errors on test 9 and 10
Date: Thu, 27 Nov 2025 14:21:20 +0100 [thread overview]
Message-ID: <2025112717-ransack-strewn-9875@gregkh> (raw)
In-Reply-To: <33c96409-b376-4e17-a2fb-a7e3bf1c3e85@kernel-space.org>
On Thu, Nov 27, 2025 at 01:53:32PM +0100, Angelo Dureghello wrote:
> Hi Greg,
>
> thanks a lot,
>
> On 11/27/25 09:22, Greg KH wrote:
> > 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.
> it's an android kernel msm-5.4, actually updated from google with critical
> fixes, at least i can see some xhci endpoint stall issues applied to it,
> even
> if of course all the usb core stuff is that old (5.4).
Again, that kernel tree will go out of support in 3 days from us, so not
much we can do here, you should seriously consider upgrading as you are
going to have a very insecure system soon (not to mention that the
latest 5.4.y release, 5.4.301, currently has 1541 unfixed CVEs in it...)
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-27 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 8:06 testusb: epipe errors on test 9 and 10 Angelo Dureghello
2025-11-27 8:22 ` Greg KH
2025-11-27 12:53 ` Angelo Dureghello
2025-11-27 13:21 ` Greg KH [this message]
2025-11-28 3:23 ` Alan Stern
2025-11-28 14:20 ` Angelo Dureghello
2025-11-28 15:20 ` Alan Stern
2025-11-28 16:10 ` Alan Stern
2025-11-28 21:21 ` Angelo Dureghello
2025-12-01 23:29 ` Thinh Nguyen
2025-12-02 3:09 ` Alan Stern
2025-12-02 4:23 ` Thinh Nguyen
2025-12-02 16:25 ` Alan Stern
2025-12-02 23:22 ` Thinh Nguyen
2025-12-04 22:26 ` Alan Stern
2025-12-10 14:20 ` Angelo Dureghello
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025112717-ransack-strewn-9875@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=angelo@kernel-space.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox