+++ This bug was initially created as a clone of Bug #667515 +++

Description of problem:

pulseaudio produces errors in / var / log / messages to start playing audio, or open the gnome mixer

Version-Release number of selected component (if applicable):

pulseaudio 0.9.21

How reproducible:

1) Open anyway player, audacious, exaile.
2) Play mp3
3) Open Sound Preferences Gnome and change tab -hardware- -input- -output-


Steps to Reproduce:
1.Open anyway player, audacious, exaile.
2.Play mp3
3.Open Sound Preferences Gnome and change tab -hardware- -input- -output-
  
Actual results:

Jan  5 16:38:54 tux pulseaudio[1636]: alsa-source.c: ALSA nos despertó para leer nuevos datos desde el dispositivo, ¡pero en realidad no hay nada para leer!
Jan  5 16:38:54 tux pulseaudio[1636]: alsa-source.c: Lo más probable es que sea un error del controlador ALSA 'snd_hda_intel'. Por favor, informe esto a los desarrolladores de ALSA.
Jan  5 16:38:54 tux pulseaudio[1636]: alsa-source.c: Nos despertaron con POLLIN puesto -- sin embargo, una llamada a snd_pcm_avail() devolvió 0 u otro valor < min_avail.
Jan  5 16:38:56 tux pulseaudio[1636]: ratelimit.c: 20 events suppressed
Jan  5 16:39:02 tux pulseaudio[1636]: ratelimit.c: 4 events suppressed


Expected results:


Additional info:

With the current kernel fedora date vmlinuz-2.6.34.7-66.fc13.i686.PAE suppressed the number of events is a value between 100 to 150.
Compiling a kernel branch 2.6.35.x with intel-HD option in the audio section, not as a module, but built into the kernel, is reduced from 4 to 40 events, at times.
This happens with some chipset like Azalia ALC888.
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
My contribution attempts to show that recompiling the kernel and putting the driver in the form of * and not as a module - [m] - the error is greatly reduced.
The kernel that was used for the test was:

http://git.kernel.org/?p=linux/kernel/git/longterm/linux-2.6.35.y.git a = summary

Did not affect the rest of the system, or as with selinux kernel 2.6.1936.
Thanks

--- Additional comment from xset1980 on 2011-01-05 15:36:08 EST ---

Created attachment 471939 [details]
config of kernel 2.6.35.10 with intel-HD

--- Additional comment from lpoetter on 2011-01-05 19:08:44 EST ---

Your ALSA driver is most likely broked. Please attach a longer excerpt of syslog (i.e. from the beginning of where it was initialized and where you played audio) and also include the output generated by alsa-info.sh --no-upload.)

--- Additional comment from xset1980 on 2011-01-05 19:39:18 EST ---

Created attachment 471969 [details]
complete /var/log/messages

--- Additional comment from xset1980 on 2011-01-05 19:40:00 EST ---

Created attachment 471970 [details]
alsa-info.sh

--- Additional comment from xset1980 on 2011-01-05 19:41:44 EST ---

(In reply to comment #2)
> Your ALSA driver is most likely broked. Please attach a longer excerpt of
> syslog (i.e. from the beginning of where it was initialized and where you
> played audio) and also include the output generated by alsa-info.sh
> --no-upload.)

Dear Lennart,

This error was reported with a vanilla 2.6.35.10 kernel, but with Fedora 13 kernel vmlinuz-2.6.34.7-66.fc13.i686.PAE happens every time you start any audio player so the messages constantly shows the errors, and even the ratelimit.c shows a value of 100 - 200 events suppressed.
With the vanilla kernel 2.6.35.10 this happens when you start the player and improves in quantity, 4 and 40 respectively (suppressed events).
I have already tried to remove pulseaudio but it still happens the same thing.
In other audio chipset, as pure Intel, no, i.e., with a Lenovo X60.

Attachments:

1.- Created attachment 471969 [details]
    complete /var/log/messages

2.- Created attachment 471970 [details]
    alsa-info.sh

--- Additional comment from xset1980 on 2011-01-21 04:08:21 EST ---

Lennart,

My alsa is good, i tested in other distro, Archlinux, Gentoo, Slackware, Debian, ubuntu, opensuse, and the bug is the same with ALC888 chipset. The problem is pulseaudio + alsa

--- Additional comment from xset1980 on 2011-01-21 04:08:55 EST ---

(In reply to comment #2)
> Your ALSA driver is most likely broked. Please attach a longer excerpt of
> syslog (i.e. from the beginning of where it was initialized and where you
> played audio) and also include the output generated by alsa-info.sh
> --no-upload.)

Lennart,

My alsa is good, i tested in other distro, Archlinux, Gentoo, Slackware,
Debian, ubuntu, opensuse, and the bug is the same with ALC888 chipset. The
problem is pulseaudio + alsa

--- Additional comment from centaur on 2011-02-20 11:15:54 EST ---

I also have the ALC888 and I have been getting spam in /var/log/messages ever since pulseaudio shipped in Fedora (11? 12?).

Feb 19 15:48:59 spike pulseaudio[3179]: ratelimit.c: 889 events suppressed
Feb 19 15:49:04 spike pulseaudio[3179]: ratelimit.c: 685 events suppressed
Feb 19 17:55:04 spike pulseaudio[3179]: ratelimit.c: 456 events suppressed
Feb 19 18:45:05 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed
Feb 19 20:05:05 spike pulseaudio[3179]: ratelimit.c: 34 events suppressed
Feb 19 22:35:05 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed
Feb 19 23:45:05 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed
Feb 20 02:15:05 spike pulseaudio[3179]: ratelimit.c: 34 events suppressed
Feb 20 02:35:08 spike pulseaudio[3179]: ratelimit.c: 34 events suppressed
Feb 20 03:55:04 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed
Feb 20 05:45:06 spike pulseaudio[3179]: ratelimit.c: 34 events suppressed
Feb 20 05:55:03 spike pulseaudio[3179]: ratelimit.c: 34 events suppressed
Feb 20 06:35:06 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed
Feb 20 07:39:31 spike pulseaudio[3179]: ratelimit.c: 35 events suppressed

--- Additional comment from centaur on 2011-02-20 11:17:00 EST ---

Created attachment 479779 [details]
alsa-info.sh output

--- Additional comment from xset1980 on 2011-03-07 03:41:13 EST ---

Per, yes, is a problem with pulseaudio, only alsa not spam in /var/log/messages, but, lennart think that my alsa is broken... i waiting for a real solution or fix

--- Additional comment from infertux on 2011-03-12 06:28:38 EST ---

Same problem here under 2.6.35.11-83.fc14.x86_64.

My /var/log/messages is flooded of:
alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
ratelimit.c: [N] events suppressed
[...]

The bug is already reported to ALSA devs: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5295

I also noticed a line maybe interesting that sometimes appears between "[N] events suppressed":
module.c: Module "module-stream-restore" should be loaded once at most. Refusing to load.

--- Additional comment from triage.org on 2011-05-30 08:10:04 EDT ---


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

--- Additional comment from centaur on 2011-05-30 10:51:48 EDT ---

This problem is still present in Fedora 14.