From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 675220 bytes (3827 ms).
Date: Tue, 25 Jan 2011 21:26:29 +0800 [thread overview]
Message-ID: <AANLkTimnWDXRGsX_-uvemsDaOCfogW44R09jA=7hiYpG@mail.gmail.com> (raw)
In-Reply-To: <4D393FA6.8050805@san.ru>
2011/1/21 support <support@san.ru>
>
>
> alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large:
> 675220 bytes (3827 ms).
> alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_emu10k1'.
> Please report this issue to the ALSA developers.
>
>
>
> http://www.alsa-project.org/db/?f=641d9cb90af2e47e527c2912bee4e34bff41b87b
>
> # rpm -qa | grep alsa
> alsa-lib-devel-1.0.23-2.fc14.i686
> alsa-plugins-pulseaudio-1.0.22-1.fc13.i686
> alsa-utils-1.0.23-3.fc14.i686
> alsa-lib-1.0.23-2.fc14.i686
>
> # uname -a
> Linux wp.san.ru 2.6.35.10-74.fc14.i686 #1 SMP Thu Dec 23 16:17:40 UTC 2010
> i686 i686 i386 GNU/Linux
>
>
>
This is underrun occur in PA server since hw_ptr is ahead of appl_ptr and
( 978317001 978195372) > buffer size 16384
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: Slave: Hardware PCM
card 0 'SB Live! [Unknown]' device
0 subdevice 0
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: Its setup is:
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: stream : PLAYBACK
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: buffer_size : 16384
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: period_size : 16384
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: appl_ptr : 978195372
Jan 21 10:55:20 wp pulseaudio[2393]: alsa-util.c: hw_ptr : 978317001
next prev parent reply other threads:[~2011-01-25 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 8:11 alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 675220 bytes (3827 ms) support
2011-01-25 13:26 ` Raymond Yau [this message]
2011-01-26 3:36 ` Raymond Yau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimnWDXRGsX_-uvemsDaOCfogW44R09jA=7hiYpG@mail.gmail.com' \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.