Description of problem: After upgrading to kernel 2.6.34.6-47.fc13.x86-64, pulseaudio crashes after a second with E: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: 614521856 bytes (3483683 ms). E: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. E: alsa-util.c: snd_pcm_dump(): E: alsa-util.c: Soft volume PCM E: alsa-util.c: Control: PCM Playback Volume E: alsa-util.c: min_dB: -51 E: alsa-util.c: max_dB: 0 E: alsa-util.c: resolution: 256 E: alsa-util.c: Its setup is: E: alsa-util.c: stream : CAPTURE E: alsa-util.c: access : MMAP_INTERLEAVED E: alsa-util.c: format : S16_LE E: alsa-util.c: subformat : STD E: alsa-util.c: channels : 2 E: alsa-util.c: rate : 44100 E: alsa-util.c: exact rate : 44100 (44100/1) E: alsa-util.c: msbits : 16 E: alsa-util.c: buffer_size : 88192 E: alsa-util.c: period_size : 44096 E: alsa-util.c: period_time : 999909 E: alsa-util.c: tstamp_mode : ENABLE E: alsa-util.c: period_step : 1 E: alsa-util.c: avail_min : 87310 E: alsa-util.c: period_event : 0 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 6205960286516543488 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 6205960286516543488 E: alsa-util.c: Slave: Hardware PCM card 0 'HDA ATI SB' device 0 subdevice 0 E: alsa-util.c: Its setup is: E: alsa-util.c: stream : CAPTURE E: alsa-util.c: access : MMAP_INTERLEAVED E: alsa-util.c: format : S16_LE E: alsa-util.c: subformat : STD E: alsa-util.c: channels : 2 E: alsa-util.c: rate : 44100 E: alsa-util.c: exact rate : 44100 (44100/1) E: alsa-util.c: msbits : 16 E: alsa-util.c: buffer_size : 88192 E: alsa-util.c: period_size : 44096 E: alsa-util.c: period_time : 999909 E: alsa-util.c: tstamp_mode : ENABLE E: alsa-util.c: period_step : 1 E: alsa-util.c: avail_min : 87310 E: alsa-util.c: period_event : 0 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 6205960286516543488 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 6205960286516543488 E: alsa-util.c: appl_ptr : 970112 E: alsa-util.c: hw_ptr : 157599104 Killed rpm -q pulseaudio pulseaudio-0.9.21-6.fc13.x86_64 reverting to kernel 2.6.33.8-149.fc13.x86_64 fixes the problem. I have been able to get pulseaudio to start a couple times, but it usually fails and I'm not sure what is different when it works.
If PulseAudio got killed, there should be something more in the system log about the reason for that.
The only thing I get in /var/log/messages are the bits I pasted into comment 0
I've got the same issue, manually updating alsa-drivers to 1.0.23 solved the problem
Created attachment 451271 [details] messages.1.log.bz2 I'm seeing the same messages after a clean F13 install and updating. The graphical pointer lags severely. The gnome volume control applet disappears briefly from the panel every few seconds. .xsession-errors is slowly filling with these: ** (gnome-settings-daemon:1910): WARNING **: Connection failed, reconnecting... ** (gnome-volume-control-applet:1960): WARNING **: Unable to get default sink ** (gnome-volume-control-applet:1960): WARNING **: Connection failed, reconnecting... ** (gnome-settings-daemon:1910): WARNING **: Connection failed, reconnecting... $ rpm -qa 'alsa*' 'pulse*' kernel gnome-media | sort alsa-lib-1.0.23-1.fc13.x86_64 gnome-media-2.30.0-1.fc13.x86_64 kernel-2.6.33.3-85.fc13.x86_64 kernel-2.6.34.7-56.fc13.x86_64 pulseaudio-0.9.21-6.fc13.x86_64 pulseaudio-gdm-hooks-0.9.21-6.fc13.x86_64 pulseaudio-libs-0.9.21-6.fc13.x86_64 pulseaudio-libs-glib2-0.9.21-6.fc13.x86_64 pulseaudio-module-bluetooth-0.9.21-6.fc13.x86_64 pulseaudio-module-gconf-0.9.21-6.fc13.x86_64 pulseaudio-module-x11-0.9.21-6.fc13.x86_64 pulseaudio-utils-0.9.21-6.fc13.x86_64
Created attachment 451272 [details] xsession-errors.1.log
(In reply to comment #4) > The gnome volume control applet disappears briefly from the panel every few > seconds. About seven seconds between flickers ...
The problem does not occur with kernel-2.6.33.3-85.fc13.x86_64, which shipped with the F13 DVD.
FWIW, I no longer see this bug after upgrading to F14 with kernel-2.6.35.6-48.fc14.x86_64. I was still seeing this with F13 (kernel-2.6.34.7-61.fc13.x86_64)
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.