Weird, I can't reproduce this problem with my self-compiled kernel :/
I don't even see soundwire modules loaded in. Manually loading them of course
doesn't do much.
Previously I could boot into the "faulty" kernel by using "recovery mode", but
I can't do that anymore - it crashes too.
Maybe there's some kind of race and this bug depends on some specific
ordering of events?
missing Kconfig?
You need CONFIG_SOUNDWIRE and CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE
selected to enter this sdw_intel_acpi_scan() routine.
