From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001074]: pcm_dmix hangs on device close
Date: Thu, 12 May 2005 13:34:27 +0200 [thread overview]
Message-ID: <3efc1d1d14f774de2c91cda7e68c93ef@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1074>
======================================================================
Reported By: ikonst
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1074
Category: pcm - digital audio
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 04-24-2005 08:48 CEST
Last Modified: 05-12-2005 13:34 CEST
======================================================================
Summary: pcm_dmix hangs on device close
Description:
The fix in pcm_dmix.c revision 1.71 causes the following regression:
Everytime I access a Flash site thru my 'aoss'-wrapped Mozilla, it hangs:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0 0x40a951c3 in poll ()
from /lib/tls/libc.so.6
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1 0x4001a1fd in poll ()
from /usr/lib/libaoss.so
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2 0x40c7bf78 in
snd_pcm_wait_nocheck (pcm=0x9a7a6a0, timeout=-1)
at pcm.c:2234
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3 0x40cb27fb in
snd_pcm_dmix_drain (pcm=0x9a7a6a0) at pcm_dmix.c:504
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4 0x40c79bd4 in
snd_pcm_drain (pcm=0xfffffffc) at pcm.c:1044
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5 0x40c8cbb7 in
snd_pcm_generic_drain (pcm=0xfffffffc) at
pcm_generic.c:151
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=6 0x40c79bd4 in
snd_pcm_drain (pcm=0xfffffffc) at pcm.c:1044
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=7 0x40bb24e7 in
lib_oss_pcm_close () from /usr/lib/libalsatoss.so.0
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=8 0x400199b4 in close ()
from /usr/lib/libaoss.so
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=9 0x441712b9 in
PlatformSoundMix::UnlockAudioCallback ()
from /usr/lib/flashplugin-nonfree/libflashplayer.so
...
======================================================================
----------------------------------------------------------------------
tiwai - 05-11-05 18:11
----------------------------------------------------------------------
Hmm, non-blocking mode should NOT block. So, if the timer behaves like you
mentioned, it must be a bug in the timer code...
----------------------------------------------------------------------
chtephan - 05-12-05 13:34
----------------------------------------------------------------------
Of, course, a non-blocking fd does not block, but the timer fd is not
opened non-blocking.
Or why do you explain he doesn't leave with EAGAIN here, but hangs in
schedule() waiting for something to happen? ;)
The pending timer event flush function should work with both blocking and
non-blocking timer fds. Except of course if the timer fds shouldn't have
been opened blocking in the first place.
> if ((file->f_flags & O_NONBLOCK) != 0 || result > 0) {
> err = -EAGAIN;
> break;
> }
>
> set_current_state(TASK_INTERRUPTIBLE);
> init_waitqueue_entry(&wait, current);
> add_wait_queue(&tu->qchange_sleep, &wait);
>
> spin_unlock_irq(&tu->qlock);
> schedule();
> spin_lock_irq(&tu->qlock);
Issue History
Date Modified Username Field Change
======================================================================
04-24-05 08:48 ikonst New Issue
05-09-05 17:33 chtephan Note Added: 0004627
05-09-05 17:53 chtephan Issue Monitored: chtephan
05-09-05 20:41 chtephan File Added: timer-flush-blocking.diff
05-09-05 20:42 chtephan Note Added: 0004629
05-11-05 17:23 ikonst Note Added: 0004638
05-11-05 18:11 tiwai Note Added: 0004639
05-12-05 13:34 chtephan Note Added: 0004641
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
next reply other threads:[~2005-05-12 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 11:34 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 11:44 [ALSA - lib 0001074]: pcm_dmix hangs on device close bugtrack
2005-05-17 15:51 bugtrack
2005-05-15 13:45 bugtrack
2005-05-13 20:57 bugtrack
2005-05-12 11:50 bugtrack
2005-05-11 16:11 bugtrack
2005-05-11 15:23 bugtrack
2005-05-09 18:42 bugtrack
2005-05-09 15:33 bugtrack
2005-04-24 6: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=3efc1d1d14f774de2c91cda7e68c93ef@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