Red Hat Bugzilla – Bug 498287
No sound after resume with snd_cs46xx
Last modified: 2010-06-28 10:45:40 EDT
Description of problem: Machine will not play any sound after suspend/resume cycle. Sound players will not advance time indicator.
Version-Release number of selected component (if applicable): Installed from F11 Preview, all updates installed.
[root@localhost ~]# modinfo snd_cs46xx
description: Cirrus Logic Sound Fusion CS46XX
author: Jaroslav Kysela <firstname.lastname@example.org>
vermagic: 184.108.40.206-111.fc11.i586 SMP mod_unload 586
parm: index:Index value for the CS46xx soundcard. (array of int)
parm: id:ID string for the CS46xx soundcard. (array of charp)
parm: enable:Enable CS46xx soundcard. (array of bool)
parm: external_amp:Force to enable external amplifer. (array of bool)
parm: thinkpad:Force to enable Thinkpad's CLKRUN control. (array of bool)
parm: mmap_valid:Support OSS mmap. (array of bool)
Steps to Reproduce:
1. Play any sound file.
2. Suspend then resume machine.
3. Attempt to play sound again.
Link to smolt profile:
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This is also reported in bug #160751 - which has been automatically closed by F9 EOL. There is a fix in an unstable branch of alsa (and has been for around a year, depending how you count) but it hasn't been pushed to the kernel.
I tried out the fix (with a modified fedora kernel) and it worked for me - but I've since updated to a new fedora kernel without the fix.
A stable link for the branch with the fix is http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-unstable-2.6.git;a=shortlog;h=topic/cs46xx-resume - again, it solves things for me.
So the fix has been in sound-unstable git for exactly a year now. Could we have it in fedora please?
*** Bug 160751 has been marked as a duplicate of this bug. ***
I asked to merge this code to the ALSA development tree on the alsa-devel maling list. It means that it will be (most probably) in next Linux kernels.
After discussion with the patch author - we had some troubles with the machine freeze after second suspend/resume cycle. Could you confirm, that the mentioned patch does not cause any machine freeze?
I'd be happy to, but I need instructions on how to do that. I'm happy to install any version of any distro and build from source, but need info on how to get it done.
(In reply to comment #9)
The machine currently has Fedora 12 installed, if that matters.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. 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 '11'.
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 11'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 11 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 to the applicable version. 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.
The process we are following is described here:
The coming 2.6.34 looks like it has patches for this. But I haven't been able to test it, nor have I attempted to rebuild the fedora 12 kernel with these patches.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.
Issue still present in Fedora 13 using kernel 220.127.116.11-124 as of June 28.
I'd be happy to contact the patch author and try out the patch. Sound is choppy on the machine now in the best case after the revamp of the sound system. I can build kernels, but need a bit more instruction. -- Chris