Bug 518772 - No sound, alsa sink timeout?
Summary: No sound, alsa sink timeout?
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-22 17:40 UTC by Brad Smith
Modified: 2009-08-24 14:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-24 14:27:53 UTC


Attachments (Terms of Use)
output of pulseaudio -vvv (48.38 KB, application/octet-stream)
2009-08-22 17:40 UTC, Brad Smith
no flags Details

Description Brad Smith 2009-08-22 17:40:03 UTC
Created attachment 358315 [details]
output of pulseaudio -vvv

Description of problem:
I've looked at the other "no sound" bugs, but they all seem slightly different than mine, so I'm opening a new one. 

For a while I was having intermittent problems with no sound being produced on my system. The mixers, including the "advanced" mixer, showed that the volume was up, and no error was produced by sound applications, and yet no sound came. 

Recently, the problem became persistent. If I kill pulseaudio and run it with -vvvv when attempting to play a sound with paplay, I see the following:

D: protocol-native.c: Underrun on '/home/brad/Sounds/receive.wav', 0 bytes in queue.
I: module-suspend-on-idle.c: Source alsa_input.pci_8086_27d8_sound_card_0 idle for too long, suspending ...
I: alsa-source.c: Device suspended...
D: alsa-sink.c: Requested volume: 0: 100% 1: 100%
D: alsa-sink.c: Got hardware volume: 0: 100% 1: 100%
D: alsa-sink.c: Calculated software volume: 0: 100% 1: 100%
D: alsa-sink.c: hwbuf_unused=0
D: alsa-sink.c: setting avail_min=87310
D: alsa-sink.c: Requested to rewind 352768 bytes.
D: alsa-sink.c: Limited to 33380 bytes.
D: alsa-sink.c: before: 8345
D: alsa-sink.c: after: 8345
D: alsa-sink.c: Rewound 33380 bytes.
D: sink.c: Processing rewind...
D: source.c: Processing rewind...
D: module-suspend-on-idle.c: Sink alsa_output.pci_8086_27d8_sound_card_0 becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.pci_8086_27d8_sound_card_0 becomes idle.
D: core.c: Hmm, no streams around, trying to vacuum.
I: sink-input.c: Freeing input 0 "/home/brad/Sounds/receive.wav"
I: client.c: Freed 1 "paplay"
I: protocol-native.c: Connection died.
I: module-suspend-on-idle.c: Sink alsa_output.pci_8086_27d8_sound_card_0 idle for too long, suspending ...
 
The full output, from startup to ^C, is attached. Other relevant information follows.

I have had this problem under at least the following kernel versions:
kernel-2.6.29.6-217.2.8.fc11.x86_64
kernel-2.6.29.4-167.fc11.x86_64
kernel-2.6.29.6-217.2.7.fc11.x86_64

Pulse and Alsa packages (note that both the i586 and x86_64 version of some packages seem to be installed. Is that normal?):

alsa-plugins-pulseaudio-1.0.20-2.fc11.i586
pulseaudio-libs-0.9.15-14.fc11.x86_64
pulseaudio-utils-0.9.15-14.fc11.x86_64
pulseaudio-module-gconf-0.9.15-14.fc11.x86_64
alsa-plugins-pulseaudio-1.0.20-2.fc11.x86_64
pulseaudio-libs-glib2-0.9.15-14.fc11.x86_64
pulseaudio-module-x11-0.9.15-14.fc11.x86_64
pulseaudio-0.9.15-14.fc11.x86_64
pulseaudio-module-bluetooth-0.9.15-14.fc11.x86_64
pulseaudio-libs-0.9.15-14.fc11.i586

alsa-lib-1.0.20-1.fc11.i586
alsa-lib-1.0.20-1.fc11.x86_64
alsa-utils-1.0.20-3.fc11.x86_64


lspci description of sound card (in a Thinkpad T60):
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)


also-info output:
http://www.alsa-project.org/db/?f=596870244759075a0e7695d25d2213a363e2e22a


This is really impairing my ability to work with this system, so if there's any other information you need, or if anyone in the Westford Red Hat office would like to see the laptop first-hand, just ask.

Comment 1 Brad Smith 2009-08-22 18:15:44 UTC
Well, this is weird. Just learned that if I plug in speakers, sounds seems to be working. Is it possible that something has disabled my laptop's internal speakers, or are they most likely just dead?

Comment 2 Lennart Poettering 2009-08-24 14:27:53 UTC
Hmm, please try if "alsactl init" fixes your issue.

Then, please try to play around with the controls in "alsamixer -c0" in the terminal. You might find an option there that reenables your internal speakers. If you did find one please file a bug against alsa-util so that this option is set by default for your hw.

I will close this now since this looks more like a driver issue or mixer initialization issue than a PA issue.


Note You need to log in before you can comment on or make changes to this bug.