Linux USB
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: "Alex Kononov" <alex@albefly.com>
Cc: "'Mathias Nyman'" <mathias.nyman@intel.com>,
	<linux-usb@vger.kernel.org>, "'Takashi Iwai'" <tiwai@suse.com>,
	<linux-sound@vger.kernel.org>
Subject: Re: xhci: unratelimited "buffer overrun event" warning floods log (~7000/s) with USB S/PDIF capture device
Date: Sat, 21 Nov 2026 10:30:29 +0100	[thread overview]
Message-ID: <20261121103029.7af20ec4.michal.pecio@gmail.com> (raw)
In-Reply-To: <001801dd7985$c068fc60$413af520$@albefly.com>

Hi,

On Sat, 21 Nov 2026 01:58:44 -0500, Alex Kononov wrote:
> Good day Mathias,
> 
> With a USB S/PDIF TX/RX adapter (Savitech, 262a:9123, UAC2, high
> speed), the xHCI driver logs an isochronous buffer overrun warning
> for nearly every microframe while the adapter's S/PDIF input has no
> signal:
> 
> xhci_hcd 0000:00:14.0: WARN: buffer overrun event for slot 2 ep 4 on
> endpoint
> 
> Rate measured: ~433,000 messages per minute (~7,200/s).
> systemd-journald sits at 100% of one core and reports "Missed N
> kernel messages".
> 
> Setup:
> - Intel N100 (PCH xHCI 0000:00:14.0), Debian 13
> - Kernel: 6.12.117+deb13-amd64 (same code in mainline 7.4-rc3)
> - Capture stream open continuously (CamillaDSP), 48 kHz S16_LE,
>   EP 0x82 IN isochronous, adaptive, 125 us interval
> - TV feeding the S/PDIF input goes idle -> no input signal -> flood.
>   With a valid input signal the count is 0.
> 
> The device is clearly misbehaving (it sends more data than requested
> when the S/PDIF receiver is unlocked; it also reports its clock source
> as valid while unlocked).

Either the device is buggy or snd_usb_audio driver submits wrong URBs,
but that's a sound subsystem issue.

> The driver handles the events correctly and audio recovers fine. The
> problem is only the logging: the warning in handle_tx_event() for
> COMP_ISOCH_BUFFER_OVERRUN is not rate-limited, so a single
> misbehaving isoc device can generate thousands of lines per second.
> 
> Locally I changed that xhci_warn() to dev_warn_ratelimited() and the
> rate dropped to ~100/min with no functional change. 
> Would a patch rate-limiting this message (or demoting it to xhci_dbg)
> be acceptable?

Not Mathias, but I think it should be xhci_dbg() like all the other
conditions which are device-triggerable rather than driver bugs.
People can still see this as -EOVERFLOW status in iso_frame_desc[].

> --- a/drivers/usb/host/xhci-ring.c
> +++ b/drivers/usb/host/xhci-ring.c
> @@ handle_tx_event()
>  	case COMP_ISOCH_BUFFER_OVERRUN:
> -		xhci_warn(xhci,
> -			  "WARN: buffer overrun event for slot %u ep %u on
> endpoint",

When submitting, please make sure to avoid line breaks like this.

Regards,
Michal

      reply	other threads:[~2026-11-21  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21  6:58 xhci: unratelimited "buffer overrun event" warning floods log (~7000/s) with USB S/PDIF capture device Alex Kononov
2026-11-21  9:30 ` Michal 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=20261121103029.7af20ec4.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=alex@albefly.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=tiwai@suse.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