Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1195868[details]
state of ALSA before the suspend
Description of problem:
When getting my laptop through suspend/resume cycle, the sound stops to
work. Sound using applications (e.g., Firefox on YouTube, or totem)
don’t look disturbed but no sound happens on the computer’s speakers.
The workaround I found for getting the sound back is to flip on/off
switch in the Sound applet of the Control Center.
Attached is the output of the alsa-info.sh script before suspend, and
after resume, while the sound was not working (and diff between the
two).
Version-Release number of selected component (if applicable):
alsa-firmware-1.0.28-2.el7.noarch
alsa-lib-1.1.1-1.el7.x86_64
alsa-lib-devel-1.1.1-1.el7.x86_64
alsa-plugins-pulseaudio-1.1.1-1.el7.x86_64
alsa-tools-firmware-1.1.0-1.el7.x86_64
alsa-utils-1.1.1-1.el7.x86_64
pulseaudio-6.0-8.el7.x86_64
pulseaudio-gdm-hooks-6.0-8.el7.x86_64
pulseaudio-libs-6.0-8.el7.x86_64
pulseaudio-libs-devel-6.0-8.el7.x86_64
pulseaudio-libs-glib2-6.0-8.el7.x86_64
pulseaudio-module-bluetooth-6.0-8.el7.x86_64
pulseaudio-module-x11-6.0-8.el7.x86_64
pulseaudio-module-zeroconf-6.0-8.el7.x86_64
pulseaudio-utils-6.0-8.el7.x86_64
How reproducible:
Steps to Reproduce:
1. suspend/resume laptop
2. run a program producing sound
3.
Actual results:
sound working
Expected results:
nothing is heard
I'd also noticed one thing. Alsa or pulse are not able to detect headphone plugged in/out. Headphone output is always activate even if I try ti plug/unplug headphone jack several times. It means for me that the sound goes always to headphones and it doesn't if they are connected or not.
(In reply to Tomas Pelka from comment #6)
> I'd also noticed one thing. Alsa or pulse are not able to detect headphone
> plugged in/out. Headphone output is always activate even if I try ti
> plug/unplug headphone jack several times. It means for me that the sound
> goes always to headphones and it doesn't if they are connected or not.
I've also experienced this. Is it worthy of a different bug report though? (some times in the rush to try and connect to video conference call on laptop you just work around the issue and I keep forgetting afterwards to investigate further).
Cliff
(In reply to Jaroslav Kysela from comment #8)
> This issue was fixed in kernel-3.10.0-498.el7 . Could you test ?
Rebooting to new kernel *seems* to be working as expected from quick test of it.
kernel-3.10.0-500.el7.x86_64 Thu 01 Sep 2016 13:48:46 BST
kernel-3.10.0-495.el7.x86_64 Fri 26 Aug 2016 13:11:26 BST
kernel-3.10.0-493.el7.x86_64 Fri 19 Aug 2016 20:00:07 BST
Suspend/resume with the kernel -500 works, but now (even with older kernels, but after yesterday's upgrade to the RHEL-7.3 Nightly) I got bug 1372427. :(
This one bug however is fine.
Created attachment 1195868 [details] state of ALSA before the suspend Description of problem: When getting my laptop through suspend/resume cycle, the sound stops to work. Sound using applications (e.g., Firefox on YouTube, or totem) don’t look disturbed but no sound happens on the computer’s speakers. The workaround I found for getting the sound back is to flip on/off switch in the Sound applet of the Control Center. Attached is the output of the alsa-info.sh script before suspend, and after resume, while the sound was not working (and diff between the two). Version-Release number of selected component (if applicable): alsa-firmware-1.0.28-2.el7.noarch alsa-lib-1.1.1-1.el7.x86_64 alsa-lib-devel-1.1.1-1.el7.x86_64 alsa-plugins-pulseaudio-1.1.1-1.el7.x86_64 alsa-tools-firmware-1.1.0-1.el7.x86_64 alsa-utils-1.1.1-1.el7.x86_64 pulseaudio-6.0-8.el7.x86_64 pulseaudio-gdm-hooks-6.0-8.el7.x86_64 pulseaudio-libs-6.0-8.el7.x86_64 pulseaudio-libs-devel-6.0-8.el7.x86_64 pulseaudio-libs-glib2-6.0-8.el7.x86_64 pulseaudio-module-bluetooth-6.0-8.el7.x86_64 pulseaudio-module-x11-6.0-8.el7.x86_64 pulseaudio-module-zeroconf-6.0-8.el7.x86_64 pulseaudio-utils-6.0-8.el7.x86_64 How reproducible: Steps to Reproduce: 1. suspend/resume laptop 2. run a program producing sound 3. Actual results: sound working Expected results: nothing is heard