From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: snd_pcm_avail_update() returning large values
Date: Fri, 6 May 2011 11:05:04 +0800 [thread overview]
Message-ID: <BANLkTimzxiYAqcmPywZtp3mV-bi=tGoQ0g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinbySDA6g40WcWYt-Yo0B-g6_B83w@mail.gmail.com>
2011/5/6 Baek Chang <baeksan@ccrma.stanford.edu>
> Hi,
>
> Occasionally, when using pulseaudio I see the following message:
>
> snd_pcm_avail_update() returned a value that is exceptionally large.
>
> This seems to be an issue with the ALSA driver itself. My question is how
> does snd_pcm_avail_update(), get updated? It uses hw buffer positions
> correct? Is there an example driver that implements snd_pcm_avail_update()
> correctly and updates buffer positions correctly?
>
> Thanks
> Baek
>
You have to provide a test case which can reproduce the problem
(e.g.http://thread.gmane.org/gmane.linux.alsa.devel/78521 )
To debug, you need to enable DEBUG_TIMING in
pulseaudio/src/modules/alsa/alsa-sink.c and
pulseaudio/src/modules/alsa/alsa-source.c
and follow
http://colin.guthr.ie/2010/09/compiling-and-running-pulseaudio-from-git/
The free-glitch mode is tailor made for snd-hda-intel , so it should be the
example driver
aplay can use minimum period size without any xrun on my snd-hda-intel
aplay -Dhw:CARD=Intel -v --period-size=32 any.wav
prev parent reply other threads:[~2011-05-06 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 0:37 snd_pcm_avail_update() returning large values Baek Chang
2011-05-06 3:05 ` Raymond Yau [this message]
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='BANLkTimzxiYAqcmPywZtp3mV-bi=tGoQ0g@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).