From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Mathias Nyman" <mathias.nyman@linux.intel.com>,
"Michał Pecio" <michal.pecio@gmail.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1
Date: Mon, 8 Apr 2024 18:42:32 +0200 [thread overview]
Message-ID: <913ed06e-56d0-4504-8af5-26ebac291d07@molgen.mpg.de> (raw)
In-Reply-To: <bd4bdabc-2d83-4022-87f4-8c599009d9f5@molgen.mpg.de>
[one addition]
Am 08.04.24 um 18:37 schrieb Paul Menzel:
> Dear Mathias, dear Michał,
>
>
> Thank you very much for your assistance.
>
>
> Am 08.04.24 um 09:17 schrieb Mathias Nyman:
>> On 7.4.2024 15.25, Michał Pecio wrote:
>>> This (and the absence of any earlier errors on the endpoint) looks
>>> like the hardware may be confirming a "successful" transfer twice or
>>> the driver may be processing one such confirmation twice.
>>
>> It's also possible this TD/TRB was cancelled due to the disconnect.
>> Could be that even if driver removes the TD from the list and cleans
>> out the TRB from the ring buffer (turns TRB to no-op) hardware may
>> have read ahead and cached the TRB, and process it anyway.
>>
>>> [ 94.088594] usb 1-2: USB disconnect, device number 8
>>> [ 94.089370] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1
>>> [ 94.089403] xhci_hcd 0000:00:14.0: Looking for event-dma 00000001250310f0 trb-start 0000000125031100 trb-end 0000000125031100 seg-start 0000000125031000 seg-end 0000000125031ff0
>>> [ 94.089427] xhci_hcd 0000:00:14.0: last xhci_td_cleanup: first_dma 1250310f0 last_dma 1250310f0 status -115 from finish_td
>>>
>>> (I say "successful" but it really isn't - the device is no longer
>>> listening. But there is no delivery confirmation on isochronous OUT
>>> endpoints so the xHC doesn't suspect anything.)
>>>
>>> Could you try again with this updated debug patch to get more info?
>>
>> Would also be helpful to add xhci dynamic debug and xhci tracing (two
>> separate logs). These will show in detail everything that is going on.
>>
>> Steps:
>>
>> 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
>> echo 1 > /sys/kernel/debug/tracing/tracing_on
>> < Reproduce issue >
>> Send output of dmesg
>> Send content of /sys/kernel/debug/tracing/trace
>>
>> please copy the /sys/kernel/debug/tracing/trace file somewhere as soon
>> as possible after reproducing the issue. It grows fast.
>
> For posterity I created Linux Kernel Bugzilla issue #218695 [1], and
> attached the files there. Hopefully everything was captured, that you
> need. The discussion could continue on this list, but do as it suits you
> best.
Just to clarify, although there are six error log lines I only plugged
and unplugged the USB headset once.
> Kind regards,
>
> Paul
>
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218695
next prev parent reply other threads:[~2024-04-08 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 10:47 xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 Paul Menzel
2024-04-05 9:32 ` Michał Pecio
2024-04-06 14:37 ` Paul Menzel
2024-04-06 16:36 ` Michał Pecio
2024-04-06 17:01 ` Paul Menzel
2024-04-07 12:25 ` Michał Pecio
2024-04-08 7:17 ` Mathias Nyman
2024-04-08 16:37 ` Paul Menzel
2024-04-08 16:42 ` Paul Menzel [this message]
2024-04-08 19:05 ` Michał Pecio
2024-04-09 11:22 ` Mathias Nyman
2024-04-10 7:59 ` Paul Menzel
2024-04-11 7:18 ` Mathias Nyman
2024-04-11 19:55 ` Paul Menzel
2024-04-13 9:17 ` Michał Pecio
2024-04-10 9:46 ` Michał Pecio
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=913ed06e-56d0-4504-8af5-26ebac291d07@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.