Red Hat Bugzilla – Bug 189006
Intel ICH Soundcard Not Activated After Suspend/Resume
Last modified: 2007-11-30 17:11:30 EST
Description of problem:
When suspending and resuming with Acer Aspire 1692WLMi laptop with an Intel ICH
soundcard, sound works all ok before suspend but when suspending and then
resuming, soundcard is not working anymore. If I run Soundcard Detection then
the card is activated again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot, start GNOME, test audio playback
2. Suspend, then resume
3. Try audio again
No sound after suspend/resume.
I'll attach my dmesg before and after suspend/resume. I'll provide any
additional info if needed. Thanks.
Created attachment 127754 [details]
dmesg output before suspending the laptop
Created attachment 127755 [details]
dmesg after resuming from suspend, soundcard not working
Created attachment 127756 [details]
dmesg after resuming from suspend and running Soundcard Detection, sound working again
So what's the status with this? Do you need more information? Thanks.
Any news about this? Do you need more information or should I wait for FC6?
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This problem still exists with kernel-2.6.18-1.2200.fc5. If you need more info
just let me know.
I plan to update to FC6 as soon as it is available and will report here status
with it, too.
ALSA bugs usually get fixed quicker by reporting them upstream to their
bugtracker at https://bugtrack.alsa-project.org/alsa-bug/
Opened an ALSA report at
I installed FC6 from scratch to my laptop but the problem still exists.
I did default Fedora 7 installation from scratch, then tried to hibernate the
machine, and this problem still exists.
Suspend doesn't resume at all so I can't verify that one but I guess if this is
not working with hibernate then also resume from suspend is not working.
I got suspend now working by patching hal-info and I can confirm that this sound
card activation problem still exists also with suspend.
Is it just a case of the card being muted, or do you need to remove and
reinsert the modules to get sound?
Could I also get you to attach the output of lspci -v and lspci -n?
Card is not just muted, setting volume up and down or mute on/off does not help
This restored all sounds:
I'll attach also lspci output.
Created attachment 157368 [details]
lspci -v output
Created attachment 157369 [details]
lspci -n output
Thanks. Since an rmmod/insmod is required, it's definitely a bug in the alsa
driver and the alsa people are the ones to poke. I'm sorry, but about all I can
do is make an account on their bugzilla and join you in poking them.
Feel free to join the party, I just added this information to ALSA bug tracker at:
Sorry for the noise but I found a related bug report with a lot of activity:
But no clear cure there either.
Great news! The problem was identified (both snd_intel8x0 and snd_intel8x0m were
resetting same registers) and the fix is available at the URL below. It will
eventually hit Linus' tree so I think it's safe to close this bug.
Actually it might be worth including the patch in the next Fedora kernel RPMs so
that suspend would work even before 2.6.24.
The patch is at:
(In reply to comment #20)
> Great news! The problem was identified (both snd_intel8x0 and snd_intel8x0m were
> resetting same registers) and the fix is available at the URL below. It will
> eventually hit Linus' tree so I think it's safe to close this bug.
I'm reviewing this as part of the kernel bug triage project:
This is marked as resolved upstream so it should be closed as requested. Please
re-open if you still have problems against 2.6.23 kernels as these should carry