Re: [PATCH] ALSA: hda/core: Log stream DMA errors on interrupt

[Michael <jagerkin@gmail.com>]

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

If there's some data I can collect let me know.

-- Mike