Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Diederik de Haas" <diederik@cknow-tech.com>
To: <linux-sound@vger.kernel.org>
Cc: <linux-rockchip@lists.infradead.org>
Subject: Endless spam in dmesg: ASoC error (-19): at snd_soc_dai_prepare() on i2s-hifi
Date: Wed, 15 Oct 2025 17:30:53 +0200	[thread overview]
Message-ID: <DDJ05640974K.3G1TLY1B75G7@cknow-tech.com> (raw)

Hi,

On several of my Rockchip based devices I get ASoC errors, where the one
from the subject occurs the most, but there are others as well.
While it should ofc be reported when an error occurs, the volume was
bad, then really bad and now it's just absurd:

root@rock5b:~# dmesg | grep -c "ASoC error (-19): at snd_soc_dai_prepare"
983

If 'dmesg' buffer can hold 1000 lines, then I have 17 of these as well:
hdmi-audio-codec hdmi-audio-codec.8.auto: HDMI: Unknown ELD version 0

This means that after just a few minutes, 'dmesg' has now become utterly
useless as it ONLY contains these errors/lines.

Booting into older kernels didn't seem to have an effect. If it had, I
could start to bisect it. I have no idea where it comes from.
So now I have removed pipewire ... and everything that depends on it ...
of which 'mpv' is the most important to me.
Now those errors are actually gone. And dmesg actually useful again.

So I guess it's triggered by (a change in) pipewire, but still the
kernel should not be generating endless copies of the same error. Once
or twice should be enough.

Can something be done about this?

Cheers,
  Diederik

             reply	other threads:[~2025-10-15 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 15:30 Diederik de Haas [this message]
2025-10-16 18:31 ` Endless spam in dmesg: ASoC error (-19): at snd_soc_dai_prepare() on i2s-hifi Diederik de Haas

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=DDJ05640974K.3G1TLY1B75G7@cknow-tech.com \
    --to=diederik@cknow-tech.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-sound@vger.kernel.org \
    /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