From: Robert Ham <rah@settrans.net>
To: "Michał Pecio" <michal.pecio@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Audio interface causing "xhci_hcd ... WARN: buffer overrun event" messages
Date: Thu, 31 Jul 2025 10:56:52 +0100 [thread overview]
Message-ID: <a574ccc8-18ac-4575-a851-38d2737d7e3e@settrans.net> (raw)
In-Reply-To: <20250731101720.5d10a8f1@foxbook>
[-- Attachment #1.1: Type: text/plain, Size: 6966 bytes --]
Hi Michał,
On 31/07/2025 09:17, Michał Pecio wrote:
> Hi,
>
> The 6.12 kernel series is half year old, so this may be unique to your
> hardware. Can you try other (ideally similar) UAC devices in the same
> USB port, or this device with different xHCI (or EHCI) controllers?
I feel I should provide some background. I've been trying to get this
device working a while. I've tried it in various machines with various
kernel versions and a number of device firmware revisions as well. The
buffer overrun errors have appeared in different places, I don't think
it's specific to this machine's controller. Regardless, I'll do your
suggested tests to make certain and get back to you.
Also, there are other problems with both the kernel and the device that
I've had to work around to get to the point of the buffer overruns in
the current setup. Firstly, I needed to add a hack to snd-usb-audio to
stop it worrying about >32 channels in a feature unit descriptor. As I
understand it though, this is a kernel issue; >32 channels is allowed.
(Patch should be forthcoming.)
Secondly, the device seems to stop responding to a SET_INTERFACE request
when snd-usb-audio sends a bunch of those requests during initialisation
so I made it send just the last request and the device seems to be OK
with that, or at least doesn't stop responding. However, I wouldn't be
surprised if it's doing silly, spec-violating things in other places
too. The manufacturer has explicitly and comically stated: "Because the
16Rig is working on Mac without any driver, it means that it is class
compliant."
--
https://forum.arturia.com/t/is-audiofuse-16rig-usb-audio-class-compliant/2153/3
> 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/
/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
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port02
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port02/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port03
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port03/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port04
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port04/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port05
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port05/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port06
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port06/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port07
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port07/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port08
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port08/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port09
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port09/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port10
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port10/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port11
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port11/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port12
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port12/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port13
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port13/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port14
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port14/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port15
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port15/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port16
/sys/kernel/debug/usb/xhci/0000:00:14.0/ports/port16/portsc
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep06
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep06/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep06/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep06/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep06/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep05
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep05/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep05/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep05/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep05/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep04
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep04/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep04/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep04/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep04/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep03
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep03/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep03/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep03/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep03/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep02
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep02/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep02/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep02/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep02/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep-context
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/slot-context
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/name
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep00
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep00/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep00/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep00/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/devices/01/ep00/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/event-ring
/sys/kernel/debug/usb/xhci/0000:00:14.0/event-ring/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/event-ring/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/event-ring/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/event-ring/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/command-ring
/sys/kernel/debug/usb/xhci/0000:00:14.0/command-ring/trbs
/sys/kernel/debug/usb/xhci/0000:00:14.0/command-ring/cycle
/sys/kernel/debug/usb/xhci/0000:00:14.0/command-ring/dequeue
/sys/kernel/debug/usb/xhci/0000:00:14.0/command-ring/enqueue
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-ext-dbc:00
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-ext-protocol:01
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-ext-protocol:00
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-ext-legsup:00
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-runtime
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-op
/sys/kernel/debug/usb/xhci/0000:00:14.0/reg-cap
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 2913 bytes --]
next prev parent reply other threads:[~2025-07-31 9:57 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 [this message]
2025-07-31 10:04 ` Robert Ham
2025-07-31 20:21 ` 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=a574ccc8-18ac-4575-a851-38d2737d7e3e@settrans.net \
--to=rah@settrans.net \
--cc=linux-usb@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox