Description of problem: I've found a vast amount of messages like Dec 28 21:49:05 rhapsody pulseaudio[3074]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. in the syslog and .xession-errors. The messages seemed to cease when I disabled glitch-free playback in Pulse. The hardware is snd_intel_hda with a Realtek 883 codec. Version-Release number of selected component (if applicable): kernel-2.6.27.10-167.fc10.x86_64 pulseaudio-0.9.13-6.fc10.x86_64 alsa-lib-1.0.18-6.rc3.fc10.x86_64 How reproducible: Extensively. Actual results: Logspam. Expected results: Fluent audio, no logspam.
I also get this behaviour on my Intel card (not the hda, but a HP laptop built in thing) Pulseaudio also seems to eat ~25% cputime while playing. Unpleasant, I think. Card: Intel 82801DB-ICH4 │ Chip: Analog Devices AD1981B │ module : snd_intel8x0
I also get this. Although in general, sound works OK. When I stream RealAudio via RealPlayer 11.0.0.4028 GOLD -- the message just spew out to syslog -- but I audio is fine. It seems to stop spewing these messages when I am not streaming audio (I still get GNOME sounds). cat /proc/asound/cards 0 [ICH5 ]: ICH4 - Intel ICH5 Intel ICH5 with AD1981B at irq 17 This is running F10 (2.6.27.9-159.fc10.i686) on and the following: alsa-lib-1.0.18-6.rc3.fc10.i386 alsa-plugins-pulseaudio-1.0.18-2.fc10.i386 alsa-lib-devel-1.0.18-6.rc3.fc10.i386 alsa-utils-1.0.18-6.fc10.i386 bluez-alsa-4.22-2.fc10.i386 pulseaudio-libs-glib2-0.9.13-6.fc10.i386 pulseaudio-esound-compat-0.9.13-6.fc10.i386 pulseaudio-libs-0.9.13-6.fc10.i386 xine-lib-pulseaudio-1.1.15-3.fc10.i386 pulseaudio-module-gconf-0.9.13-6.fc10.i386 pulseaudio-0.9.13-6.fc10.i386 pulseaudio-utils-0.9.13-6.fc10.i386 pulseaudio-module-bluetooth-0.9.13-6.fc10.i386 alsa-plugins-pulseaudio-1.0.18-2.fc10.i386 pulseaudio-libs-zeroconf-0.9.13-6.fc10.i386 pulseaudio-core-libs-0.9.13-6.fc10.i386 pulseaudio-module-x11-0.9.13-6.fc10.i386
See bug 471941, comment 8 for a workaround for your message log filling up.
*** This bug has been marked as a duplicate of bug 486068 ***