Sound stopped to work

[Lukast]

I use Fedora 10, with default audio system - pulse audio
I use KDE with KPackage Kit, automatic updates turned on.
Sound stopped to work.

lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)

Dec 26 12:32:54 pavilon pulseaudio[3416]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 268432644 bytes (1521727 ms) Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers.
Dec 26 12:32:56 pavilon pulseaudio[3416]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 377340 bytes (2139 ms) Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers.
Dec 26 12:32:56 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:56 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.
Dec 26 12:32:57 pavilon pulseaudio[3416]: 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.

/var/log/yum.log from last days:

Dec 22 12:41:36 Updated: compiz-0.7.8-4.fc10.i386
Dec 22 12:41:37 Updated: xdg-utils-1.0.2-5.20081121cvs.fc10.noarch
Dec 22 12:41:40 Updated: compiz-fusion-0.7.8-2.fc10.i386
Dec 22 12:41:53 Updated: compiz-fusion-gnome-0.7.8-2.fc10.i386
Dec 22 12:42:32 Updated: compiz-gnome-0.7.8-4.fc10.i386
Dec 22 12:42:33 Updated: perl-Git-1.6.0.6-1.fc10.i386
Dec 22 12:42:45 Updated: git-1.6.0.6-1.fc10.i386
Dec 22 23:04:24 Updated: nash-6.0.71-3.fc10.i386
Dec 22 23:04:25 Updated: mkinitrd-6.0.71-3.fc10.i386
Dec 24 17:39:50 Installed: libmikmod-3.2.0-3.beta2.fc9.i386
Dec 24 17:39:51 Installed: 1:xmms-libs-1.2.11-3.20071117cvs.fc10.i386
Dec 24 17:39:51 Installed: xmms-pulse-0.9.4-6.fc10.i386
Dec 24 17:39:52 Installed: paman-0.9.4-2.fc9.i386
Dec 24 17:39:53 Installed: padevchooser-0.9.4-0.6.svn20070925.fc10.i386
Dec 24 17:39:54 Installed: paprefs-0.9.7-3.fc10.i386
Dec 24 17:39:54 Installed: pavumeter-0.9.3-2.fc9.i386
Dec 25 14:42:40 Updated: kernel-firmware-2.6.27.9-159.fc10.noarch
Dec 25 14:43:06 Installed: kernel-devel-2.6.27.9-159.fc10.i686
Dec 25 14:43:06 Updated: kmodtool-1-14.fc10.noarch
Dec 25 14:43:09 Updated: kernel-headers-2.6.27.9-159.fc10.i386
Dec 25 14:43:13 Updated: bcel-javadoc-5.2-5.1.fc10.i386
Dec 25 14:43:39 Updated: kdelibs3-3.5.10-3.fc10.i386
Dec 25 14:43:39 Updated: audit-libs-1.7.10-1.fc10.i386
Dec 25 14:44:07 Installed: kernel-2.6.27.9-159.fc10.i686
Dec 25 14:44:13 Updated: kdelibs3-devel-3.5.10-3.fc10.i386
Dec 25 14:44:14 Updated: fakeroot-1.11-19.fc10.i386
Dec 25 14:44:15 Updated: xorg-x11-drv-ati-6.9.0-63.fc10.i386
Dec 25 14:44:15 Updated: audit-libs-python-1.7.10-1.fc10.i386
Dec 25 14:44:16 Updated: audit-1.7.10-1.fc10.i386
Dec 25 14:44:25 Updated: bcel-5.2-5.1.fc10.i386
Dec 25 14:44:26 Installed: kmod-nvidia-2.6.27.9-159.fc10.i686-177.82-1.fc10.7.i686
Dec 25 14:44:26 Updated: kmod-nvidia-177.82-1.fc10.7.i686
Dec 25 14:44:27 Installed: 9:kdevelop-libs-3.5.4-1.fc10.i386
Dec 25 14:44:58 Updated: 9:kdevelop-3.5.4-1.fc10.i386
Dec 25 14:45:26 Installed: kernel-2.6.27.9-159.fc10.i686

Do you know any workaround? Please help.

[Lukast]

After investigation it seems that new kernel is problem here.
I'm going to report bug in bugzilla.

[Boricua]

Hi, please take a look at these threads, they might help:

http://forums.fedoraforum.org/showthread.php?t=208756

http://forums.fedoraforum.org/showthread.php?t=208791

[Lukast]

Thanks.

Using older kernel resolved my problem. And here is bugzilla entry:
https://bugzilla.redhat.com/show_bug.cgi?id=477888