From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218695] Datadump for error `ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1`
Date: Tue, 09 Apr 2024 11:24:52 +0000 [thread overview]
Message-ID: <bug-218695-208809-8wSzgthLh7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218695-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218695
--- Comment #2 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
The trace shows hosts sends duplicate transfer events for ISOC TRBs
after a Transaction error on same device. This transaction error is probably
due to device disconnect.
Transfer events for TRB ..a1c0 twice, with a transaction error in between:
<idle>-0 [000] d.h2. 33819.709897: xhci_handle_event: EVENT: TRB
00000032959a1c0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event' flags
e:c
<idle>-0 [000] d.h2. 33819.709904: xhci_handle_event: EVENT: TRB
000000041547d010 status 'USB Transaction Error' len 4 slot 6 ep 15 type
'Transfer Event' flags e:c
systemd-journal-395 [000] d.H1. 33819.711886: xhci_handle_event: EVENT:
TRB 000000032959a1c0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event'
flags e:c
Transfer events for TRB ..a1d0 twice (the next TRB)
systemd-journal-395 [000] d.H1. 33819.712001: xhci_handle_event: EVENT:
TRB 000000032959a1d0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event'
flags e:c
systemd-journal-395 [000] d.H1. 33819.712059: xhci_handle_event: EVENT:
TRB 000000032959a1d0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event'
flags e:c
Transfer events for TRB ..a1e0 twice
systemd-journal-395 [000] d.H1. 33819.712139: xhci_handle_event: EVENT:
TRB 000000032959a1e0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event'
flags e:c
systemd-journal-395 [000] d.h1. 33819.712871: xhci_handle_event: EVENT:
TRB 000000032959a1e0 status 'Success' len 0 slot 6 ep 2 type 'Transfer Event'
flags e:c
etc..
Driver can cope with these extra events, but if this is common we should
probably handle it silently and not concern users with that ERROR message.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-04-09 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 16:31 [Bug 218695] New: Datadump for error `ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1` bugzilla-daemon
2024-04-08 16:34 ` [Bug 218695] " bugzilla-daemon
2024-04-09 11:24 ` bugzilla-daemon [this message]
2024-04-12 7:40 ` bugzilla-daemon
2025-02-27 21:44 ` bugzilla-daemon
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=bug-218695-208809-8wSzgthLh7@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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;
as well as URLs for NNTP newsgroup(s).