Bug 216499
| Summary: | MOTU M2 : snd_pcm_hw_params failed: Device or resource busy | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Matteo Beniamino (m.beniamino) |
| Component: | Sound(ALSA) | Assignee: | Jaroslav Kysela (perex) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | tiwai |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.19.9 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Output of alsa-info.sh
Output of spa-acp-tool -vvv -c 5 in kernel 5.19.7 Output of spa-acp-tool -vvv -c 5 in kernel 5.19.9 |
||
Created attachment 301823 [details]
Output of spa-acp-tool -vvv -c 5 in kernel 5.19.7
Created attachment 301824 [details]
Output of spa-acp-tool -vvv -c 5 in kernel 5.19.9
As noted in https://bugzilla.kernel.org/show_bug.cgi?id=216500 , this could be the same issue and reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.19.y&id=271f862ebc60b3a7ff1563654eb33cd4571c66aa fixes it for me. Yes, this must be the same. *** This bug has been marked as a duplicate of bug 216500 *** |
Created attachment 301822 [details] Output of alsa-info.sh After upgrading to 5.19.9 pipewire won't create any profile for my MOTU M2 interface. With kernel 5.19.8 it's working as expected. I'm using alsa-ucm-conf at commit 3a6acaa5090a0c5a0d29c8a4906b6a60378774e2 , that is a commit after the official 1.2.7.2 release: that commit fixes the ucm profile for the M2. I've found out that "spa-acp-tool -vvv -c 5" gives different output in the two cases. Here is an excerpt of the interesting lines. kernel 5.19.7: ``` Maximum hw buffer size is 100 ms Set buffer size first (to 4800 samples), period size second (to 1200 samples). Device hw:M2 doesn't support sample format s16le, changed to s32le. Profile Direct supported. ALSA device close 0x5635c1df90b0 ``` kernel 5.19.9: ``` Maximum hw buffer size is 100 ms Set neither period nor buffer size. snd_pcm_hw_params failed: Device or resource busy ALSA device close 0x5618eebc2130 ``` (as I wrote I eventually tested with 5.19.8 and the interface still works). This behaviour is consistent, the only difference between the tests was the kernel version. I'm using the kernel from my distro (Arch), but I've checked that there were no patches applied or options changed between the two releases.