Red Hat Bugzilla – Bug 432956
Sound card locked after suspend/resume cycle
Last modified: 2013-03-05 22:54:43 EST
Description of problem:
After a suspend/resume cycle in Gnome, my snd_intel8x0 ends up
locked/monopolised by some (as yet unidentified) application. Other ALSA
programs cannot find the sound card (e.g., alsamixer, alsacard). Logging out and
back in again fixes this. I'm not using PulseAudio. Filing under alsa-utils
since I don't know which of the following components is to blame:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3. Run alsamixer, alsacard, etc.
Sound card "not found" or otherwise unavailable.
Sound as normal.
Examples of output:
[james@harmony ~]$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device
[james@harmony ~]$ alsacard
Open error: No such device
If you identify which normally loaded modules are associated with your card, you
might be able to rmmod them and then modprobe them to make it work again (much
less drastic than reboot). I have a TV tuner card which doesn't work after
suspend unless I rmmod and then modprobe the associated modules.
It doesn't require anything so drastic ;) I don't need to go so far as module
reloads, this seems to be a userspace issue. I should point out that the problem
isn't as consistent as I first thought. When I tried switching to a text-mode
console and logged in as root, alsa-mixer ran fine. Switched back to X and
normal sound service resumed... possibly a ConsoleKit bug?