Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Arun Raghavan <arunr@valvesoftware.com>
To: Takashi Iwai <tiwai@suse.de>, Arun Raghavan <arunr@valvesoftware.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Arun Raghavan" <arun@arunraghavan.net>
Subject: Re: [External Mail] Re: [PATCH] ALSA: hda/core: Log stream DMA errors on interrupt
Date: Tue, 4 Aug 2026 10:42:17 -0700	[thread overview]
Message-ID: <DKGCFDZL0ZPJ.WU7CLZ8ZJKOI@valvesoftware.com> (raw)
In-Reply-To: <87tspai11y.wl-tiwai@suse.de>

On Tue Aug 4, 2026 at 4:21 AM PDT, Takashi Iwai wrote:
> On Tue, 04 Aug 2026 00:07:52 +0200,
> Arun Raghavan wrote:
>> 
>> The stream descriptor status register reports FIFO and descriptor
>> errors, but these are currently cleared silently along with the rest
>> of the interrupt status. Log them, rate-limited, so DMA problems are
>> visible instead of only manifesting as audible glitches.
>> 
>> Observed on some AMD GPU HDMI audio controllers under specific low power
>> circumstances.
>> 
>> Signed-off-by: Arun Raghavan <arunr@valvesoftware.com>
>> Cc: Arun Raghavan <arun@arunraghavan.net>
>
> Applied now to for-next branch.
>
> It's interesting at which situation you get the error bit and which
> one.  If it can be used *reliably* for catching a streaming error, the
> driver could notify XRUN or error appropriately, too.

Ah, I should have mentioned that in the commit message. The error bit
that was signalled was SD_INT_FIFO_ERR -- the status byte was read as
(SD_STS_FIFO_READY | SD_INT_FIFO_ERR).

We are still working on pinning down the precise cause in this case, but
it seems to be related to issues in some specific setups during lower
frequency memory clock transitions. The error manifests as a short
dropout caused by what appears to be a stall or missed transfer. The
frequency of dropouts varies from several per minute to one every few
minutes.

In such a case, the existence of XRUNs might be good to know further up
the stack, though it isn't clear that there is much that userspace can
autonomously do to mitigate the it.

Cheers,
Arun


  reply	other threads:[~2026-08-04 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 22:07 [PATCH] ALSA: hda/core: Log stream DMA errors on interrupt Arun Raghavan
2026-08-04 11:21 ` Takashi Iwai
2026-08-04 17:42   ` Arun Raghavan [this message]
2026-08-04 18:18     ` [External Mail] " Takashi Iwai
2026-08-05 20:56       ` Arun Raghavan
2026-08-06  6:30         ` Takashi Iwai

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=DKGCFDZL0ZPJ.WU7CLZ8ZJKOI@valvesoftware.com \
    --to=arunr@valvesoftware.com \
    --cc=arun@arunraghavan.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox