From: "Michał Pecio" <michal.pecio@gmail.com>
To: Martin Maurer <martin.maurer@mmeacs.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: Problem hanging Bulk IN, with USB 3.x, perhaps due to wMaxPacketSize = 1024 and wMaxBurst = 6 (OUT) and 2 (IN), tested and reproduceable with i.MX8MP and Raspberry Pi Compute Module 5 (CM5)
Date: Thu, 14 Aug 2025 14:16:32 +0200 [thread overview]
Message-ID: <20250814141632.43ded731@foxbook> (raw)
In-Reply-To: <64e36d3b-606f-4fa7-bb6a-1dfd8a144de6@mmeacs.de>
Hi,
On Fri, 8 Aug 2025 23:47:07 +0200, Martin Maurer wrote:
> What can I do/test next?
>
> Try again on a AMD x64 controller? Perhaps with main/latest of Linux Kernel?
You are describing some fairly complex setups, can you confidently
say that the problem is USB and not elsewhere? For example, you have
tcpdump running on the USB host machine and packets go out through
the USB network interface but nothing comes back?
What driver are you using with this USB device? Any errors/diagnostics
from the driver, or from xhci_hcd (I guess that's your host)?
You tried usbmon and what happened? Is the driver submitting IN URBs?
Are they coming back empty? With error status? Not completing at all?
Trying on a PC with newer kernel makes sense, debugging may be easier
that way and lower risk of:
- chasing bugs in downstream kernels that nobody here can help with
- fixing something that has already been figured out and fixed
Regards,
Michal
next prev parent reply other threads:[~2025-08-14 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 21:47 Problem hanging Bulk IN, with USB 3.x, perhaps due to wMaxPacketSize = 1024 and wMaxBurst = 6 (OUT) and 2 (IN), tested and reproduceable with i.MX8MP and Raspberry Pi Compute Module 5 (CM5) Martin Maurer
2025-08-14 12:16 ` Michał Pecio [this message]
2025-08-14 13:02 ` Mathias Nyman
2025-08-17 14:58 ` Martin Maurer
2025-08-17 15:07 ` Martin Maurer
2025-08-17 15:22 ` Daniele Palmas
2025-08-17 17:01 ` Martin Maurer
2025-08-18 19:49 ` Daniele Palmas
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=20250814141632.43ded731@foxbook \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=martin.maurer@mmeacs.de \
/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