From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - firmware 0000209]: Sometimes XMMS stop playing songs (dmix used)
Date: Wed, 12 Jan 2005 10:41:06 +0100 [thread overview]
Message-ID: <85c2023eba4239186ca254f7bfa7d259@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=209>
======================================================================
Reported By: srr
Assigned To:
======================================================================
Project: ALSA - firmware
Issue ID: 209
Category:
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 04-14-2004 11:41 CEST
Last Modified: 01-12-2005 10:41 CET
======================================================================
Summary: Sometimes XMMS stop playing songs (dmix used)
Description:
Sometimes XMMS stop playing songs and show message that says "Audio device
not
properly configured or busy". It happends when new song just start
playing. If I click on Play button, songs continued playing.
I can't repeat this bug, it happends 3-5 times in day.
If i start mpg123 and xmms they are play simultaniously (even if i start
10
copies of mpg123)
This is output from xmms:
ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device
or resource busy
ALSA lib pcm_dmix.c:868:(snd_pcm_dmix_open) unable to open slave
** WARNING **: alsa_setup(): Failed to open pcm device (default): Device
or
resource busy
======================================================================
----------------------------------------------------------------------
martin - 11-28-04 18:33
----------------------------------------------------------------------
At least my rme32 problems are fixed in CVS. (see also bug
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=611 for a
patch)
----------------------------------------------------------------------
leahcim - 01-12-05 10:41
----------------------------------------------------------------------
I also see this mmap+dmix problem on two machines. Pausing and unpausing
XMMS (rather than restarting the track) is sufficient to make sound output
resume normally. Occasionally all sound-playing processes (ie. aplay,
which I use for all system & mail alert sounds) will log-jam behind any
xmms or aplay process that halts in this way.
ALSA 1.0.6 on kernels 2.6.10-rc3 and 2.6.10, running Debian sarge.
I82801BAICH2 and CMI8738 audio hardware respectively.
Issue History
Date Modified Username Field Change
======================================================================
04-14-04 11:41 srr New Issue
04-16-04 11:54 tiwai Note Added: 0000832
04-20-04 07:39 srr Note Added: 0000869
04-20-04 07:41 srr Issue Monitored: srr
10-14-04 22:40 chtephan Note Added: 0002160
10-20-04 20:42 martin Note Added: 0002218
11-28-04 18:33 martin Note Added: 0002626
01-12-05 10:41 leahcim Note Added: 0003161
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-12 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 9:41 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 14:13 [ALSA - firmware 0000209]: Sometimes XMMS stop playing songs (dmix used) bugtrack
2006-06-28 4:35 bugtrack
2006-03-22 2:06 bugtrack
2005-07-20 23:03 bugtrack
2005-01-19 15:54 bugtrack
2004-11-28 17:33 bugtrack
2004-10-20 18:42 bugtrack
2004-10-14 20:40 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=85c2023eba4239186ca254f7bfa7d259@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.