From: "Michał Pecio" <michal.pecio@gmail.com>
To: Robert Ham <rah@settrans.net>
Cc: linux-usb@vger.kernel.org
Subject: Re: Audio interface causing "xhci_hcd ... WARN: buffer overrun event" messages
Date: Thu, 31 Jul 2025 22:21:16 +0200 [thread overview]
Message-ID: <20250731222116.79b15493@foxbook> (raw)
In-Reply-To: <87114caf-7c0d-4e51-bb3e-f171fc20ac62@settrans.net>
On Thu, 31 Jul 2025 11:04:40 +0100, Robert Ham wrote:
> On 31/07/2025 09:17, Michał Pecio wrote:
> > Can you mount debugfs and see if you can find the directory below? It
> > would tell if there is anything unusual about those 1 in 65 buffers.
> >
> > /sys/kernel/debug/usb/xhci/0000:00:14.0/
>
> Umm.. and this is with the device connected and snd-usb-audio loaded,
> which might be more helpful :-)
>
> /sys/kernel/debug/usb/xhci/0000:00:14.0/
> /sys/kernel/debug/usb/xhci/0000:00:14.0/ports
> /sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port01
> /sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port01/portsc
> [...]
Actually, the useful stuff would be contents of some of those files,
but the trace you posted later provides similar information. And it
looks like you will need to dig into snd-usb-audio some more.
FYI, scripts/get_maintainer says that the relevant mailing list for
that driver is linux-sound.
Regards,
Michal
prev parent reply other threads:[~2025-07-31 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 20:02 Audio interface causing "xhci_hcd ... WARN: buffer overrun event" messages Bob Ham
2025-07-31 8:17 ` Michał Pecio
2025-07-31 8:27 ` Michał Pecio
2025-07-31 10:11 ` Robert Ham
2025-07-31 14:26 ` Mathias Nyman
2025-08-02 8:43 ` Robert Ham
2025-07-31 9:56 ` Robert Ham
2025-07-31 10:04 ` Robert Ham
2025-07-31 20:21 ` Michał Pecio [this message]
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=20250731222116.79b15493@foxbook \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=rah@settrans.net \
/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