[REGRESSION] No audio on kernel 6.17.8 - Intel Lunar Lake CS42L43 (works on 6.17.7)

General system Kernel, boot, graphics & hardware
1

Hi everyone,

Just ran into an audio regression after updating from kernel 6.17.7 to 6.17.8 on my Lenovo Yoga with Intel Core Ultra 5 228V (Lunar Lake).

Working: linux 6.17.7-arch1-1
Broken: linux 6.17.8-arch1-1, linux-zen 6.17.8-zen1-1-zen, linux-lts 6.12.59-1-lts

Downgrading to 6.17.7 brings audio back.

dmesg shows:
platform cs42l43-spi: deferred probe pending: cs42l43-spi: Failed to register SPI controller platform sof_sdw: deferred probe pending: sof_sdw: snd_soc_register_card failed -517

Hardware: Intel Lunar Lake, Cirrus Logic CS42L43 codec via SoundWire.

I opened an upstream issue here: https://github.com/thesofproject/linux/issues/5603

Sharing in case anyone else hits this.

Workaround:
sudo downgrade linux linux-headers

Pick version 6.17.7, then add to IgnorePkg until it’s fixed upstream.

Cheers!

1 Like
2

Thanks for the report!

Since it seems to be a regression in the kernel 6.17.8, perhaps the sof project github is not the right place to report the issue.

There seem to be several reports about this already across different distributions:

https://bbs.archlinux.org/viewtopic.php?id=310227

Perhaps more relevant:

3

Thank you.

I wanted to post on https://bugzilla.kernel.org/ but there is the message: “Please use your distribution’s bug tracking tools. This bugzilla is for reporting bugs against upstream Linux kernels.”

On the Arch forum, I read that it is only for the “real” Arch distribution.

So, would the best place be GitLab Arch?
https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues

4

Since the bug seems to be non distro specific, I doubt Arch’ maintainers can do much about it unless they have reverted the bad commit causing the regression in 6.17.9 which is in core-testing repo at the moment.

What I understood form the Arch forum thread I posted before, the issue was not present in some -rc versions of 6.18.

So, if 16.17.9 won’t fix the issue, perhaps we have to wait for the stable release of 6.18 which may be a couple of weeks away.

But by all means, if you want, file a bug report at the link you have posted in your reply.