From: "Michał Pecio" <michal.pecio@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
Mathias Nyman <mathias.nyman@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org,
Niklas Neronin <niklas.neronin@linux.intel.com>
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: Sat, 13 Apr 2024 11:17:46 +0200 [thread overview]
Message-ID: <20240413111746.059dd4b7@foxbook> (raw)
In-Reply-To: <fca78115-209f-4090-b83b-acc684484587@molgen.mpg.de>
> Thank you for the detailed analysis. Excuse my ignorance, but do you
> have an idea, what this Sennheiser USB headset does differently than
> other USB devices?
It uses isochronous out transfers, which off the top of my head are
almost only used for audio playback in the real world.
However, I don't know what it is doing differently from your other USB
headset. A few random hypotheses:
- the other is not a "full speed" device (but it most likely is)
- you haven't tried enough times to reproduce the bug
- you have some software which automatically starts playback to the
Sennheiser when it's connected, but not to the other headset
- different playback format and different USB packet size, although
192B/ms corresponds to 16 bit 48kHz stereo - the most comomn format.
As for your bugzilla comment and the list of other TRB mismatch errors
on linux-hardware - yes, these things happen due to a variety of bugs
in host controllers and the driver. They are not all the same bug and
they can't be analyzed or fixed if people don't report them and don't
cooperate in debugging. These messages alone don't provide information
about what specifically went wrong and under which circumstances.
Regards,
Michal
next prev parent reply other threads:[~2024-04-13 9:17 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
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 [this message]
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=20240413111746.059dd4b7@foxbook \
--to=michal.pecio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=niklas.neronin@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
/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.