alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Gregan <kinetik@flim.org>
To: alsa-devel@alsa-project.org
Subject: Re: Hang in snd_pcm_writei with alsa-pulse plugin
Date: Tue, 2 Nov 2010 17:44:21 +1300	[thread overview]
Message-ID: <20101102044421.GA2588@flim.org> (raw)
In-Reply-To: <AANLkTikxDrqXGVwk=-dGokWWxbHyeLKNEZzM3pvH2QKv@mail.gmail.com>

At 2010-11-02T10:43:54+0800, Raymond Yau wrote:
> No much response because there are bugs in atest2.c
> 
>   /* prefill sound buffers and begin playback */
>   fill(pcm);
> 
>   while (++count) {
> 
> The program had filled the buffer but the output does not indicate those
> write

This doesn't affect the result of the testcase.  count is only used to pause
and resume less frequently than every iteration of the write loop.

> I can confirm that the program seem hang after a few pause/unpause when
> using alsa-pulse plugin
> 
> However it assert when using hw device
> 
>   assert(bsize / psize >= 4);

The assert is present because I've only tested on systems where this
assertion holds true.  It's likely that the loop timing would need to be
changed to work correctly in other cases.

Thanks for confirming that you can reproduce the problem.  I've since
discovered that it's possible to produce the same problem with the
PulseAudio API directly, so I'll take this up on pulseaudio-discuss@.

Cheers,
-mjg
-- 
Matthew Gregan                     |/
                                  /|                    kinetik@flim.org

  reply	other threads:[~2010-11-02  4:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01  1:38 Hang in snd_pcm_writei with alsa-pulse plugin Matthew Gregan
2010-11-01 17:30 ` Colin Guthrie
2010-11-02  2:43   ` Raymond Yau
2010-11-02  4:44     ` Matthew Gregan [this message]
2010-11-02  8:23       ` Raymond Yau
2010-11-09 12:20       ` Raymond Yau
2010-11-04  3:29 ` Raymond Yau
2010-11-04  3:52   ` Matthew Gregan
2010-11-22 23:55 ` Raymond Yau
2011-05-06 13:46 ` 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=20101102044421.GA2588@flim.org \
    --to=kinetik@flim.org \
    --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).