From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001091]: dmix hangs on 2nd-3rd snd_pcm_drop
Date: Tue, 9 Aug 2005 13:44:34 +0200 [thread overview]
Message-ID: <1a971256d4facbade9859e0524c7e65e@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1091>
======================================================================
Reported By: ikonst
Assigned To: tiwai
======================================================================
Project: ALSA - lib
Issue ID: 1091
Category: 0_general
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 05-06-2005 17:48 CEST
Last Modified: 08-09-2005 13:44 CEST
======================================================================
Summary: dmix hangs on 2nd-3rd snd_pcm_drop
Description:
Rhythmbox performs a "drop" upon pressing Pause. When playing thru a dmix
device, toggling pause-play a couple of time (one or two is enough) will
cause alsa-lib to hang. Here's the relevant stack trace:
#0 0x40be8741 in __read_nocancel () from /lib/tls/libpthread.so.0
#1 0x444790a8 in snd_timer_hw_read (handle=0xbfffdcc8,
buffer=0xfffffe00,
size=8) at timer_hw.c:184
#2 0x44478a7a in snd_timer_read (timer=0x8, buffer=0xbfffdcc8, size=8)
at timer.c:879
#3 0x44465cbd in snd_pcm_direct_clear_timer_queue (dmix=0x8883020)
at pcm_direct.c:429
#4 0x44465cfd in snd_pcm_direct_timer_stop (dmix=0x8883020)
at pcm_direct.c:437
#5 0x44468744 in snd_pcm_dmix_drop (pcm=0xfffffe00) at pcm_dmix.c:475
#6 0x4442fb24 in snd_pcm_drop (pcm=0xfffffe00) at pcm.c:1021
#7 0x443cf985 in gst_alsa_hw_params_dump ()
from /usr/lib/gstreamer-0.8/libgstalsa.so
...
======================================================================
----------------------------------------------------------------------
tiwai - 05-24-05 12:31
----------------------------------------------------------------------
Fixed on 1.0.9rc4.
Issue History
Date Modified Username Field Change
======================================================================
05-06-05 17:48 ikonst New Issue
05-24-05 12:31 tiwai Status new => resolved
05-24-05 12:31 tiwai Resolution open => fixed
05-24-05 12:31 tiwai Assigned To => tiwai
05-24-05 12:31 tiwai Note Added: 0004720
08-09-05 13:44 perex Status resolved => closed
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-09 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 11:44 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 10:31 [ALSA - lib 0001091]: dmix hangs on 2nd-3rd snd_pcm_drop bugtrack
2005-05-06 15:48 bugtrack
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=1a971256d4facbade9859e0524c7e65e@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.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