Created attachment 446679 [details] alsa-info.sh output when I have sound Description of problem: Since the 2.6.34 kernels were pushed, I randomly "lose" my sound card at boot times. See http://www.alphatek.info/2010/09/04/sound-is-gone-who-should-i-blame/ Version-Release number of selected component (if applicable): kernel-2.6.34.6-47.fc13.i686, kernel-2.6.34.6-54.fc13.i686 (same behaviour on all 2.6.34 kernels) How reproducible: I lose my sound card about 1/3 of the times I boot my computer. Steps to Reproduce: 1. Boot the computer 2. Look in the Gnome sound preferences under "output" 3. There should be 2 sound cards listed as you can see on the blog's screenshot. Instead, only the "RV710/730 Digital Stereo (HDMI)" is listed when the other sound card is "gone". Additional info: lspci -vvv output for the sound card: 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: ASRock Incorporation Device 2888 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin ? routed to IRQ 16 Region 0: Memory at fe9f0000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
Created attachment 446680 [details] alsa-info.sh output when I have NO sound
Interesting... when you have no sound you are getting these messages in the log: ALSA sound/pci/hda/hda_intel.c:711: azx_get_response timeout, switching to polling mode: last cmd=0x001f000a ALSA sound/pci/hda/hda_intel.c:750: hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x001f000a But there's no obvious reason why that would happen. Can you attach /var/log/messages from when it's working and when it's broken?
Created attachment 449613 [details] /var/log/messages when I have sound
Created attachment 449614 [details] /var/log/messages when I have NO sound
As requested, the 2 /var/log/message files are attached as they appear after a reboot. Since I opened the ticket, kernel-2.6.34.7-56.fc13.i686 has been installed on the system but the problem still persists.
Since I reported the issue, the PC has been upgraded to Fedora 14 beta and now final and the issue has completely disappeared...I guess that we can close this ticket as there is no software/hardware combination to test it anymore?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.