[Bug 1191247] New: audio goes to mono after waking up from sleep
https://bugzilla.suse.com/show_bug.cgi?id=1191247 Bug ID: 1191247 Summary: audio goes to mono after waking up from sleep Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: pandre.x@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- hey everybody. I got this issue with regards to the audio coming from my USB sound card (Audient iD14): every time I put the pc on sleep and wake it up, every single source of audio goes to mono and I can hear the music/sounds coming just from one of my two speakers. I did update to PipeWire, however the issue continues as it was with PulseAudio or Jack. To fix that I can either plug my usb sound card off and plug back in or restart the pc. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pandre.x@gmail.com, | |tiwai@suse.com Flags| |needinfo?(pandre.x@gmail.co | |m) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- I'm building a kernel with a backport from the upstream commit that might be relevant. It's being built in OBS home:tiwai:bsc1191247 repo. It'll be available later (after an hour or so) at http://download.opensuse.org/repositories/home:/tiwai:/bsc1191247/standard/ Please give it a try later. Note that it's an unofficial build, hence it won't boot with Secure Boot. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- (In reply to Andrea P from comment #4)
(In reply to Takashi Iwai from comment #3)
Thanks for quick testing.
Then could you load alsa-info.sh output from the patched kernel after suspend/resume? Run the script with --no-upload, and use Bugzilla attachment.
Thank you. Sorry but I have no idea how to run this script. where is located? so sorry, I'm not that expert :D
It's /usr/sbin/alsa-info.sh included in alsa-utils package. It should have been already installed. Just run it as root with --no-upload option, and attach the generated file to Bugzilla (don't paste, it's big).
- Check whether the problem persists with suspend-to-RAM and suspend-to-disk (hibernate). I assume you're dealing with the former, right?
Hibernate it doesn't work on my PC (maybe because I don't have a swap partition?).
Right, hibernate works only with a swap (or other dedicated) partition.
- Last but not least, check whether re-loading the driver fixes the problem without re-plugging. You might need to go out of desktop session once, unload snd-usb-audio module and re-load snd-usb-audio module on Linux console.
Again, so sorry but I don't know how to stop and re-load this module.
OK, then to make things easier: - Try to boot with a boot option "3" This will boot to Linux console without GUI - Login there, plug USB-audio device, test directly via aplay % aplay -Dplughw:XXX foo.wav as mentioned in the above. - Do suspend/resume % systemctl suspend - Check again aplay and confirm the mono output - Unload / reload the module % sudo modprobe -r snd-usb-audio % sudo modprobe snd-usb-audio - Test aplay again -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- The next step is try to adjust the mixer values manually after suspend/resume and see whether it influences on the behavior. Unfortunately the alsactl contents are empty in alsa-info.sh outputs by some reason. Could you run the following as root, and attach to Bugzilla? alsactl -f /tmp/alsactl.out store -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- And if the option above helps, please try the kernel again in the URL mentioned in comment 1. It was rebuilt with a new patch. Don't forget to drop the modprobe.d stuff you've added for the previous test before trying it out. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c19 --- Comment #19 from Andrea P <pandre.x@gmail.com> --- (In reply to Takashi Iwai from comment #13)
The next step is try to adjust the mixer values manually after suspend/resume and see whether it influences on the behavior.
Unfortunately the alsactl contents are empty in alsa-info.sh outputs by some reason. Could you run the following as root, and attach to Bugzilla?
alsactl -f /tmp/alsactl.out store
Hi, I forgot to attach the alsactl.out I was able to generate after creating 60-usb-audio.conf Hopefully it will says why my right channel is lower in volume. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c20 --- Comment #20 from Andrea P <pandre.x@gmail.com> --- Created attachment 853327 --> https://bugzilla.suse.com/attachment.cgi?id=853327&action=edit alsactl.out -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191247 https://bugzilla.suse.com/show_bug.cgi?id=1191247#c22 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(pandre.x@gmail.co | |m) | --- Comment #22 from Takashi Iwai <tiwai@suse.com> --- OK, then let's close. Feel free to reopen if you encounter the same problem again. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com