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 13:32:04 +0200 [thread overview]
Message-ID: <20260910133204.3157f83b.michal.pecio@gmail.com> (raw)
In-Reply-To: <20260910110453.1528072-1-scarabeeta@gmail.com>
On Thu, 10 Sep 2026 20:04:53 +0900, wakasio wrote:
> I looked for the offending TRB in the dump, attached is the full log
> (dyndbg_capture4_trb_dump.log, 1061 lines).
The attachment seems to be missing.
> The 11 xhci_dbg lines all say "Transfer error for slot 1 ep 3", same
> address ffffd140425178e0, resid 23552, each followed by "Soft-reset ep
> 3". After the 11th one the driver printed "event ring:" and dumped it,
> then "endpoint ring:" and dumped that too.
>
> I searched the endpoint ring dump for the DMA address that the event
> ring entries point to. I could not find it. The endpoint ring dump
> covers two segments, 0xfffc00000 to 0xfffc00ff0 and 0xfffbf0000 to
> 0xfffbf0ff0, linked back to each other with a Link TRB. The address in
> question, 0xfffbf8e0, falls between these two ranges, not inside
> either one.
Not sure what happened, I'd like to see the full dump. It's possible
that my patch is wrong and logged some addresses incorrectly, but
I think it should have logged the correct ring and the events must
have matched the ring, or otherwise other errors would be logged.
> I also noticed the event ring entries pointing to that address are all
> labeled "ep 4", not "ep 3".
Yes, 4 is the number used by xHCI, 3 is a driver-internal equivalent.
Regards,
Michal
next prev parent reply other threads:[~2026-09-10 11:32 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 [this message]
2026-09-10 11:38 ` wakasio
2026-09-10 12:16 ` Michal Pecio
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=20260910133204.3157f83b.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®