From: John Lindgren <john.lindgren@tds.net>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: snd_pcm_drop causing lockup with DMix
Date: Mon, 01 Mar 2010 18:52:32 -0500 [thread overview]
Message-ID: <1267487552.11621.2.camel@satellite> (raw)
In-Reply-To: <alpine.LNX.2.00.1003010752570.28127@eeebox2.perex-int.cz>
Still no difference.
I also noticed that with or without the patch, Audacious will
occasionally not hang up, and instead the snd_pcm_writei call that is
interrupted will return -EBADFD. I haven't seen the test case do the
same.
On Mon, 2010-03-01 at 07:53 +0100, Jaroslav Kysela wrote:
> And this one?
>
> diff --git a/src/pcm/pcm_direct.c b/src/pcm/pcm_direct.c
> index d9e596e..ae32fab 100644
> --- a/src/pcm/pcm_direct.c
> +++ b/src/pcm/pcm_direct.c
> @@ -540,7 +540,6 @@ void snd_pcm_direct_clear_timer_queue(snd_pcm_direct_t *dmix)
> int snd_pcm_direct_timer_stop(snd_pcm_direct_t *dmix)
> {
> snd_timer_stop(dmix->timer);
> - snd_pcm_direct_clear_timer_queue(dmix);
> return 0;
> }
>
> @@ -1274,6 +1273,7 @@ int snd_pcm_direct_set_timer_params(snd_pcm_direct_t *dmix)
> snd_timer_params_set_ticks(params, 1);
> if (dmix->tread) {
> filter = (1<<SND_TIMER_EVENT_TICK) |
> + (1<<SND_TIMER_EVENT_STOP) |
> dmix->timer_event_suspend |
> dmix->timer_event_resume;
> snd_timer_params_set_filter(params, filter);
>
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.
next prev parent reply other threads:[~2010-03-01 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 15:37 snd_pcm_drop causing lockup with DMix John Lindgren
2010-02-28 16:22 ` Jaroslav Kysela
2010-02-28 17:15 ` John Lindgren
2010-03-01 6:53 ` Jaroslav Kysela
2010-03-01 23:52 ` John Lindgren [this message]
2010-03-02 13:25 ` Jaroslav Kysela
2010-03-03 0:24 ` John Lindgren
2010-03-03 10:01 ` Jaroslav Kysela
2010-03-03 12:28 ` John Lindgren
2010-03-03 12:59 ` Jaroslav Kysela
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=1267487552.11621.2.camel@satellite \
--to=john.lindgren@tds.net \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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).