Red Hat Bugzilla – Bug 155705
no sound after ACPI resume
Last modified: 2015-01-04 17:19:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2
Description of problem:
I have IBM ThinkPad T23 laptop.
After sleep (ACPI`s S3 mode) the sound completely disappears, until either:
1) rmmod/insmod for appropriate snd-* module
alsactl power D3
alsactl power D0
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Play any sample, make sure all is OK
2. Go to sleep by "echo 3 >/proc/acpi/state "
3. Resume by pressing appropriate button(s)
4. Play any sound again
Actual Results: Unlike 1), no more sound at all
It is old issue, first was reported as bug 127210 for fc2...
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
Unfortunately, nothing changed with the new kernel-2.6.12-1.1376_FC3 ...
I have the same issue with FC4 and 2.6.12-1.1456_FC4.
which sound modules are in use here ?
snd_intel8x0m 19845 0
snd_intel8x0 34945 11
snd_ac97_codec 76217 2 snd_intel8x0m,snd_intel8x0
snd_seq_dummy 3781 0
snd_seq_oss 37569 0
snd_seq_midi_event 9409 1 snd_seq_oss
snd_seq 62801 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 9037 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 51569 0
snd_mixer_oss 18113 2 snd_pcm_oss
snd_pcm 100553 5
snd_timer 33733 10 snd_seq,snd_pcm
snd 57669 21
soundcore 11169 2 snd
snd_page_alloc 9925 3 snd_intel8x0m,snd_intel8x0,snd_pcm
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
This issue does seem to be fixed in the 1526 kernel.
I initially reported it on FC3...
BTW, any plans to update new kernel for FC3 too?
not to 2.6.13 level. I will backport various fixes, but I don't know if I'm
going to root-cause this to a specific patch in time for whats likely to be the
final FC3 update before it reaches end of life.
Now I've upgraded my laptop (IBM ThinkPad T23), under the latest kernel 2.6.18
the issue still exist.
The same behavior/symptomes/workarounds as before.
Should be fixed in the next kernel update.
Could you please confirm whether it is fixed or not by a more recent kernel?
Still not fixed with latest FC5 kernel, based on upstream's 22.214.171.124 .
Cannot check under 2.6.21 for a while...
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Still present, at least under Fedora 7
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.