mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arun Raghavan" <arun@arunraghavan.net>
To: Michael <jagerkin@gmail.com>, arunr@valvesoftware.com
Cc: "Takashi Iwai" <tiwai@suse.de>, "Takashi Iwai" <tiwai@suse.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	alexander.deucher@amd.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Peter Ujfalusi" <peter.ujfalusi@linux.intel.com>
Subject: Re: [PATCH] ALSA: hda/core: Log stream DMA errors on interrupt
Date: Sun, 15 Nov 2026 19:25:24 -0800	[thread overview]
Message-ID: <5b34b0ef-9eef-4049-a018-3e60bda634f8@app.fastmail.com> (raw)
In-Reply-To: <20261026013835.98210-1-jagerkin@gmail.com>

On Sun, 25 Oct 2026, at 6:38 PM, Michael wrote:
> On Wed Aug 19, 2026 at 11:53 AM PDT, Arun Raghavan wrote:
>> On Wed Aug 5, 2026 at 11:30 PM PDT, Takashi Iwai wrote:
>>> So what's the best option for users if this happens?
>>> That is, what happens if we don't restart the stream?  Is it a
>>> temporary fail-out and the hardware recovers / resync by itself while
>>> streaming further?  If so and it's short, it might be better to leave
>>> it as is.
>>
>> Unfortunately, there doesn't appear to be much users can do in this
>> state. The warnings we have introduced should at least point to a cause,
>> but the issues seem to be around GPU clocks and power management
>
> A data point from Intel hardware, where there are no obvious issues
> with playback quality.
>
> 7.3.0 logs this continuously as soon as PipeWire opens the analog
> playback stream:
>
>   snd_hda_intel 0000:00:1f.3: stream 7 dma error: 0x28
>
> Per include/sound/hda_register.h, 0x28 is FIFO_READY | FIFO_ERR, the
> same bits you reported.
>
> The only open PCM is pcm0p (2ch, 48 kHz, period 1024, buffer 32768
> frames), so I'm assuming that's stream 7.
>
> Counting the callbacks suppressed, it's something like 7-8/second.
>
> ThinkPad X1 Yoga 3rd gen:
> * i7-8650U, Sunrise Point-LP HDA 8086:9d71 subsystem 17aa:2259
> * Realtek ALC285
> * snd_hda_intel
> * no dGPU

Hum, that's not great. I'm not aware of what the Intel hardware might be doing. Maybe Peter (cc'ed) does?

-- Arun

      reply	other threads:[~2026-11-16  3:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 22:07 Arun Raghavan
2026-08-04 11:21 ` Takashi Iwai
2026-08-04 17:42   ` [External Mail] " Arun Raghavan
2026-08-04 18:18     ` Takashi Iwai
2026-08-05 20:56       ` Arun Raghavan
2026-08-06  6:30         ` Takashi Iwai
2026-08-19 18:53           ` Arun Raghavan
2026-10-26  1:38             ` Michael
2026-11-16  3:25               ` Arun Raghavan [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=5b34b0ef-9eef-4049-a018-3e60bda634f8@app.fastmail.com \
    --to=arun@arunraghavan.net \
    --cc=alexander.deucher@amd.com \
    --cc=arunr@valvesoftware.com \
    --cc=jagerkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --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

all inboxes | Powered by JetHome®