5.10.63 causes 1000s of lines of errors relating to hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19

[graysky2]

Describe the bug

1. When kodi starts, dmesg is polluted with thousands of lines like this:

   hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19

2. If I start my RPi4 with the attached TV off, the RPi4 does not detect that an external monitor is connected and the only way to enable HDMI output is to reboot the RPi4 with the TV on.

Downgrading to 5.10.59-1 fixes both issues. There are only 5 lines in dmesg displaying that error. That kernel is based on this commit: https://github.com/raspberrypi/linux/commit/22201d4868f66aa7773d5c4bad7bab1795ee6757

To reproduce

• Install 5.10.63-1 on Arch ARM aarch64 (https://github.com/raspberrypi/linux/commit/597cd63b48c6dc3746827504f191744c120fbb4d)
• Start kodi

Expected behaviour

1. dmesg should not be spammed with 1000s of lines
2. HDMI detection should work regardless of TV on/off state

Actual behaviour

1. dmesg is spammed with 1000s of lines.
2. HDMI detection is broken relative to 5.10.59

System Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

• Which model of Raspberry Pi? RPi4B Rev 1.4
• Which OS and version? Arch ARM aarch64
• Which firmware version (vcgencmd version)?

  Aug 31 2021 14:52:47 
  Copyright (c) 2012 Broadcom
  version 67615e950e1e28b92dfae6303cf7a8b879a8908f (clean) (release) (start)

• Which kernel version (uname -a)? Linux treetop 5.10.63-1-ARCH #1 SMP PREEMPT

Logs If applicable, add the relevant output from dmesg or similar.

Additional context Add any other relevant context for the problem.

[acavalin]

Ops, forgive me 🙏🏻 I didn't know that tool and I'm afraid to update the kernel with it, I'll wait for the next kernel package update 👍🏻

[SteffenDuenner]

I was so brave to rpi-update and there are no more messages in dmesg! Great work! ;)

[iball]

Just to add my own experience, I saw these same errors as well but they went away after an rpi-update.

[LeGeek01]

I have the same error, but this error cancel the session opening of user "pi" and go back to the login screen in loop. After a rpi-update, the error went away but a new appears:

déc. 29 15:48:50 raspberrypi pulseaudio[753]: Failed to find a working profile.
déc. 29 15:48:50 raspberrypi pulseaudio[753]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef0570 argument: "device_id="2" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=y 0.hdmi" namereg_fail=false tsched=no fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): in es use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
déc. 29 15:48:50 raspberrypi lightdm[960]: pam_unix(lightdm:session): session closed for user pi

[LeGeek01]

fixed, the problem was a full sdcard...

[rabotond]

Having this problem since I updated 2-3 days ago my raspberry pi 400. Running Ubuntu 22.10 on it. Linux myhome-pi 5.19.0-1013-raspi #20-Ubuntu SMP PREEMPT Wed Jan 18 14:37:07 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I would appreciate some help, Not sure how to fix it. There is no display on my tv (no signal).

[mcprat]

in general you should get support from Ubuntu forums since you're using their kernel

the problem with the displays is separate from the errors that you posted, which is HDMI audio

only thing I can recommend is look at the discussion above about kernel command line property "video" so you can manually set the resolution and "force enable" for the display

if I remember correctly, the problem I had was the display had to be connected and powered on before booting the raspberry pi, otherwise it was never detected. if you can confirm that current behavior then setting the video property in kernel command line will likely fix it.

[popcornmix]

The message is typically harmless. See https://github.com/xbmc/xbmc/pull/22471

I'll close this as issue no longer occurs on RPiOS. If you have this issue on another distribution, then report it there with a link the referenced PR and they can apply the fix.