From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: 5.11.17: xhci_hcd 0000:0a:00.3: WARN Event TRB for slot 3 ep 12 with no TDs queued?
Date: Mon, 3 May 2021 11:57:41 +0300 [thread overview]
Message-ID: <6a4c37df-8403-4026-6ff2-189ce1e87264@linux.intel.com> (raw)
In-Reply-To: <18f75805-2538-476f-38bb-d3c6e1c2bf5e@xs4all.nl>
Hi
On 2.5.2021 18.22, Udo van den Heuvel wrote:
> Hello,
>
> When 5.11.17 gives me a load of:
>
> xhci_hcd 0000:0a:00.3: WARN Event TRB for slot 3 ep 12 with no TDs queued
>
> What happened?
Either your host is sending spurious events, or more likely this TD (transfer descriptor)
was already handled and given back by driver due some event mid TD.
Host still has this TD cached and generates events for last entry of TD after xhci driver gave it back.
> What can I do (to help) fix it?
First try 5.12 (just came out) It has some xhci driver changes in this area.
If that doesn't help please take dynamic debug logs and xhci traces:
mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
< trigger the issue >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace
Trace can be huge, dmesg helps me find the right place in trace.
Thanks
-Mathias
next prev parent reply other threads:[~2021-05-03 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 15:22 5.11.17: xhci_hcd 0000:0a:00.3: WARN Event TRB for slot 3 ep 12 with no TDs queued? Udo van den Heuvel
2021-05-03 8:57 ` Mathias Nyman [this message]
2021-05-25 5:35 ` Udo van den Heuvel
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=6a4c37df-8403-4026-6ff2-189ce1e87264@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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).