Description of problem: it seems that - with some frequency - I lose all sound. I see this in dmesg: [15423.399140] ALSA sound/pci/hda/hda_intel.c:894 azx_get_response timeout, switching to polling mode: last cmd=0x01970700 [15424.489683] ALSA sound/pci/hda/hda_intel.c:902 No response from codec, disabling MSI: last cmd=0x01970700 [17144.109449] ALSA sound/pci/hda/hda_codec.c:236 hda_codec: resetting BUS due to fatal communication error All access to sound devices (such as by pulseaudio) fails, and pulseaudio is stuck in an unkillable state. Thus far, the only fix is to reboot.
post the output of alsa-into.sh
Created attachment 685181 [details] alsa info The changelog for kernel 3.7.3 looks like it contains some fixes for Intel HDA that might be relevant here.
Created attachment 714330 [details] Another alsa-info
In my case, only the mic stop working. No workaround. This issue appear since upgrade to 3.8.1-201.fc18.x86_64. No problem at all in my case with 3.7.8-202.fc18.x86_64.
(In reply to comment #3) > Created attachment 714330 [details] > Another alsa-info you should open another report and post the pulseaudio verbose log if you are using different hda codec Codec: Cirrus Logic CS4213 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10134213 Subsystem Id: 0x1028055c Revision Id: 0x100100 No Modem Function Group found Default PCM: rates [0x0]: bits [0x0]: formats [0x0]: Default Amp-In caps: N/A Default Amp-Out caps: N/A GPIO: io=2, o=0, i=0, unsolicited=1, wake=1 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0xb041d: Stereo Amp-Out Control: name="Master Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name="Master Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="Cirrus Analog", type="Audio", device=0 Amp-Out caps: ofs=0x73, nsteps=0x7f, stepsize=0x01, mute=1 Amp-Out vals: [0x73 0x73] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Delay: 11 samples Node 0x04 [Pin Complex] wcaps 0x410581: Stereo Control: name="Headphone Jack", index=0, device=0 Pincap 0x0000001c: OUT HP Detect Pin Default 0x0421101f: [Jack] HP Out at Ext Right Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Delay: 1 samples Connection: 1 0x02 Node 0x05 [Pin Complex] wcaps 0x420581: Stereo Control: name="Speaker Phantom Jack", index=0, device=0 Pincap 0x00000050: OUT Balanced Pin Default 0x90170010: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Delay: 2 samples Connection: 1 0x02
Are you still seeing this issue with 3.9.y kernels?
Hi, As requested I opened another bug for my specific case : Bug 924618. Issue was quite similar and has been solved. I not experiencing any issue since 3.9-2. Kind regards.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days