mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: wakasio <scarabeeta@gmail.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: xhci_hcd / ASMedia ASM4242: Bulk-OUT -EPROTO with Logitec 0789:0308 during DVD+RW recording
Date: Thu, 10 Sep 2026 14:16:33 +0200	[thread overview]
Message-ID: <20260910141633.00892cf8.michal.pecio@gmail.com> (raw)
In-Reply-To: <20260910113946.1546390-1-scarabeeta@gmail.com>

On Thu, 10 Sep 2026 20:38:43 +0900, wakasio wrote:
> Sorry, I do not know why the attachment did not go through. Pasting
> the full log below instead.

Thanks. Here's the repeating error event:

TRB 00000000fffbf8e0 status 'USB Transaction Error' len 23552 slot 1 ep 4 type 'Transfer Event' flags e:c

In three runs so far, it always shows 23KB remaining out of 32KB and
that's the only consistent pattern. It happened quite far from any
segment boundary this time, practically in the middle of a segment.

My patch logged TRB addresses wrong and added a zero in the middle:

fffbf08b0: Buffer 00000000fffbd000 length 31 TD size 0 intr 0 type 'Normal' flags b:i:I:c:s:i:e:C
fffbf08c0: Buffer 00000000ff620000 length 32768 TD size 0 intr 0 type 'Normal' flags b:i:I:c:s:i:e:C
fffbf08d0: Buffer 00000000fffbd000 length 31 TD size 0 intr 0 type 'Normal' flags b:i:I:c:s:i:e:C
fffbf08e0: Buffer 00000000ff628000 length 32768 TD size 0 intr 0 type 'Normal' flags b:i:I:c:s:i:e:C

Nothing special is happening here, it's just a single 32KB buffer,
aligned to 32KB, not crossing any 64KB boundary. TD size is 0 as it
should be for the last (and only) TRB of a TD, chain bit is clear,
only IOC and cycle are set. Next TRB's cycle still isn't set:

fffbf08f0: Buffer 00000000ff670000 length 32768 TD size 0 intr 0 type 'Normal' flags b:i:I:c:s:i:e:c

So I don't know what's wrong with it, I think it's a HW bug happening
for no obvious reason. Retries aren't helping for 100ms, so the HW
seems to be stuck for good in some invalid state.

And it only happens with one combination of host and device, so we
can't even be sure which side is wrong. Maybe the most sensible
solution is to simply stop using this device with this host and keep
watching for firmware upgrades.

Regards,
Michal

  reply	other threads:[~2026-09-10 12:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 15:46 wakasio
2026-09-04 18:30 ` Michal Pecio
2026-09-05  3:10   ` wakasio
2026-09-05  8:18     ` Michal Pecio
2026-09-05 13:45       ` wakasio
2026-09-05 21:49         ` Michal Pecio
2026-09-06  2:13           ` wakasio
2026-09-06 10:15             ` Michal Pecio
2026-09-06 10:27             ` Michal Pecio
2026-09-08 10:49               ` wakasio
2026-09-08 11:10                 ` Michal Pecio
2026-09-10 11:04                   ` wakasio
2026-09-10 11:32                     ` Michal Pecio
2026-09-10 11:38                       ` wakasio
2026-09-10 12:16                         ` Michal Pecio [this message]
2026-09-10 12:55                           ` wakasio

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=20260910141633.00892cf8.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=scarabeeta@gmail.com \
    /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

all inboxes | Powered by JetHome®