-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sof-audio-pci-intel-tgl error messages piling on DMESG #5220
Comments
@rfsalomon, the prints like
are printed because PA/PW is probing all PCMs of the sound cards and since you have NVIDIA dGPU, the HDMI via Intel display is not working, they are physically disconnected. Can you attach the output of |
Here they are. |
Understood. However, these lines should not appear on the console when the user logs in without a shell, should they? |
You have misspelled option to select the legacy driver snd-intel-dspcf.dsp_driver=1 -> snd-intel-dspcfg.dsp_driver=1 Right, I see now in the dmesg/alsa-info log:
the display codec is not connected and in this case SOF needs to treat the HDMI audio PCM devices as dummy ones, they are created, but they will no work and they will eventually throw an error, which is unfortunate. The problem is that the topology files we have assumes that there is always HDMI audio. I'm sure this machine is not the first with such setup and so far they have worked somehow. I do agree t hat the prints are not nice in the console. |
@ujfalusi This seems like a user-space problem. alsa-info shows that no HDMI/DP PCMs are created for integrated graphics and dummy codecs are plugged in instead. So for kernel this is as expected. alsa-info also shows no controls for HDMI/DP for the SOF device, so user-space elements should NOT try to open the SOF devices. For some reaosn some user-space entity keeps on opening the dummy HDMI/DP entities (even if kcontrols say there's nothing connected) and the resulting error is to be expected (you can't actually stream to the dummy codec). That's a good question which component and why in user-space is making this call. I'm guessing this is using Pipewire. Pipewire logs would be the next place to check -- i.e. what's in the log when kernel sees open on the dummy HDMI/DP PCMs. |
Yes, it is wireplumber which probes the PCMs to figure out their capabilities. fwiw, I can reproduce it on my gaming laptop with |
I think it is the pro-audio profile probing which is opening all PCM devices, it is unconditionally goes through all cards and all PCM device via add_pro_profile() I don't see a way to disable this. |
indeed, dropping the call to |
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3407 @rfsalomon, I think it would be best to create a bug for Pipewire and add a link to this issue to work out a solution. |
Will do. I'll post the bug link here for reference. Thanks! [edit] https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/1835 |
The issue upstream moved to https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4405 |
System information:
Operating System: openSUSE Tumbleweed 20241025
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × 12th Gen Intel® Core™ i7-12850HX
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA RTX A2000 8GB Laptop GPU/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 21D6S16900
System Version: ThinkPad P16 Gen 1
The following messages keep being written to DMESG:
sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp1 Pin: -22
This message repeats 20 times before changing to
sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp1 Pin: -22
Which repeats 20 times and changes to
sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp3 Pin: -22
Which also repeats for 20 times before going back to iDisp1 and continuing the cycle
The driver logs the following information before entering the error message cycle:
Sound works fine but the sheer amount of error messages logged caught my eye.
Additional information:
The text was updated successfully, but these errors were encountered: