From: Michal Pecio <michal.pecio@gmail.com>
To: Gabriel Ilie <gabiilie95@gmail.com>
Cc: linux-usb@vger.kernel.org, mathias.nyman@intel.com,
linux-sound@vger.kernel.org
Subject: Re: xhci 8086:7a60 (HM770) skips ~9.5% of isoc OUT packets when hot; HDA on same PCH underruns in step
Date: Fri, 20 Nov 2026 21:30:50 +0100 [thread overview]
Message-ID: <20261120213050.18641baf.michal.pecio@gmail.com> (raw)
In-Reply-To: <CAHJAn3zOCh8oKjE9fVbeD_XbnSG-h8psZWan9qkNji_mps8rFA@mail.gmail.com>
Hi,
On Mon, 16 Nov 2026 16:05:13 -0500, Gabriel Ilie wrote:
> 1. Is a periodic ~1 ms inability to service periodic endpoints a known
> behaviour of the 700-series PCH when it is hot (PCH thermal
> throttling, DMI, or something else)? Is there a way to read the PCH's
> throttle state or temperature on this platform to confirm it?
No idea, but it seems you found clear correlation with temperature.
Maybe the proper solution is more heatsinking and airflow.
> 2. The controller advertises CFC (hcc params bit 11), so as far as I
> understand the isoc TDs carry explicit frame IDs and the ones whose
> frame has passed are skipped after the Missed Service Error. For a
> UAC2 async device with its own buffer, sending those packets late
> would probably be inaudible, while dropping 1 ms is not. Would using
> SIA instead of frame IDs be acceptable here, perhaps as a quirk or an
> option I can test?
Somebody recently added quirk flag "PLAYBACK_URB_FIXUP" to
snd_usb_audio which submits playback URBs with SIA. AFAIK there
is some way to try those quirks with a module parameter.
It may reduce the number of missed microframes, but I doubt
it will make the glitches inaudible. There is no such thing as
transmitting an isochronous packet "later", it must be skipped
if it doesn't make it on time.
Regards,
Michal
prev parent reply other threads:[~2026-11-20 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 21:05 xhci 8086:7a60 (HM770) skips ~9.5% of isoc OUT packets when hot; HDA on same PCH underruns in step Gabriel Ilie
2026-11-20 20: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=20261120213050.18641baf.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=gabiilie95@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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