Pipewire - suspended -> error (Start error: Invalid argument)

[mikefaille]

When I use pipewire and I try to connect directly 2 interface, I have this error :

ct 02 17:52:51 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:51 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:51 pop-os pipewire[19565]: spa.alsa: Broken configuration for playback: no configurations available: Invalid argument
Oct 02 17:52:51 pop-os pipewire[19565]: pw.node: (alsa_input.usb-Focusrite_Scarlett_18i8_USB_F96G6XP1283E26-00.pro-input-0-69) suspended -> error (Start error: Invalid argument)
Oct 02 17:52:54 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:54 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:54 pop-os pipewire[19565]: spa.alsa: Broken configuration for playback: no configurations available: Invalid argument
Oct 02 17:52:54 pop-os pipewire[19565]: pw.node: (alsa_input.usb-Focusrite_Scarlett_18i8_USB_F96G6XP1283E26-00.pro-input-0-69) suspended -> error (Start error: Invalid argument)
Oct 02 17:52:57 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:57 pop-os pipewire[19565]: spa.alsa: Broken configuration: no configurations available: Invalid argument
Oct 02 17:52:57 pop-os pipewire[19565]: spa.alsa: Broken configuration for playback: no configurations available: Invalid argument
Oct 02 17:52:57 pop-os pipewire[19565]: pw.node: (alsa_input.usb-Focusrite_Scarlett_18i8_USB_F96G6XP1283E26-00.pro-input-0-69) suspended -> error (Start error: Invalid argument)

Can it be an issue at driver side ? I documented the error on Pipewire side too : https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1995

[mikefaille]

@geoffreybennett According the Pipewire main dev this error is unknown from him and come from Alsa : https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1948#note_1227101

Now, my Pro Profile under pipewire don't work with the microphone and it's related to the error log above too.

[mikefaille]

cc: @sadko4u are you testing pipewire too ?

[geoffreybennett]

Hi Mike, if you disable the mixer driver (remove the module device_setup option or set to 0, then confirm dmesg says "Focusrite Scarlett Gen 2/3 Mixer Driver disabled") does that fix the problem?

[mikefaille]

I have the same issue (with full details from pipewire logs, dmesg lines and no monitor on pavucontrol for my focusright - works with jack2 ) :

Here is my pw-dump result : pipewire-setup0.log

My pipewire version : 0.3.44-1~ubuntu21.10 Wireplumber version : 0.4.7.r24.gda023e1-1~ubuntu21.10 Kernel : pop-os 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb

[geoffreybennett]

That's a pipewire or alsa problem then, unrelated to the mixer driver. Next step: does going back to kernel 5.10 fix the problem?

[mikefaille]

@geoffreybennett It does work with the kernel 5.10.

Here is my test to reproduce it :

1. getting the kernel 5.10 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/
2. starting on recovery mode (as my Nvidia module doesn't compile)
3. systemctl isolate multi-user
4. login with my user to bring the same pipewire config.
5. using pulsemixer to make sure my Scarlet focusrite 18i8 is the default input and I use the pro mode
6. using parecord out.wav to record my audio
7. my audio file is actually working testing with vlc

If I use the kernel 5.15 with the steps 5. to 7. the audio file is empty.

Here is my pw-dump for the kernel 5.10 : pw-dump5.10.log

^ this dump may contain the pulseaudio profile configuration.

[mikefaille]

@geoffreybennett I don't know if you saw my answer or if it's appropriate on opensource project to ping someone as you are free to help; I'm sorry if it's not the case. I just wanted to know if you saw my answer. I'm ready to help at your desire.

[geoffreybennett]

Hi Mike, thanks for the ping. As the problem seems unrelated to the mixer driver, and only dependent on the kernel version, that would indicate to me that it's a problem with the ALSA driver. I would suggest subscribing to the alsa-devel mailing list at https://alsa-project.org/wiki/Mailing-lists and asking on there. I see that Tobias Guggenmos here: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1948#note_1240242 tried narrowing down the issue with a git bisect but failed. If you could do a git bisect and identify the broken commit, that would be very helpful in finding/fixing the issue.

[mikefaille]

I just created a ticket on the Kernel bug tracker : https://bugzilla.kernel.org/show_bug.cgi?id=215792

I just subscribe to the Alsa-dev mailing list wishing some feedback.

For the kernel dissect, I would as soon I have time ! At least, my focus is trying to make sure this issue is well documented.

[mikefaille]

@geoffreybennett Thank you ! It seems we found the issue ! A Linux patch is incoming ! https://bugzilla.kernel.org/show_bug.cgi?id=215792#c33

[geoffreybennett]

Thanks for pointing that out! This patch also fixed the same issue I was having with my Qu-16.