From: Christophe Saout <christophe@saout.de>
To: Jan Knutar <jk-lkml@sci.fi>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>,
alsa-user@lists.sourceforge.net
Subject: Re: XMMS (or some other audio player) 'hang' issues with intel8x0 and dmix plugin [u]
Date: Tue, 02 Nov 2004 12:52:09 +0100 [thread overview]
Message-ID: <1099396329.713.4.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <200411021340.03164.jk-lkml@sci.fi>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Am Dienstag, den 02.11.2004, 13:40 +0200 schrieb Jan Knutar:
> > I've tracked this down to what seems to be a bug in the libalsa dmix
> > code with mmap emulation. If the sound output was stopped for some
> > reason (stream paused or underrun) the library will accept more data
> > until the buffer is full but never restart the output.
>
> Strangely, I've observed these kinds of "Hangs" with bmp and mplayer,
> without mmap mode enabled in either. Also using dmix as in the other
> reports here. Could of course be some third application using alsa in
> mmap mode, I suppose.
It might have something to do whether dmix needs to convert the data or
not. In my case /proc shows that the card supports 48kHz but bmp plays a
44kHz file.
> Unfortunately, I have no strace to offer right now as the bug is happening
> randomly and I haven't been able to find any method by which to reproduce
> it.
100% reproducable on my machine. I stopped debugging when I found out
that it happened somewhere deep inside the libalsa dmix core, the code
didn't look easy to follow.
> What's strange is that almost always when it happens, either mplayer or
> beep-media-player will have an extra forked process.
This has something to do with dmix forking off a process, I don't know
exactly what it is for, it does something with the dmix unix socket
in /tmp.
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-02 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 4:42 Martin Schlemmer [c]
2004-11-02 7:43 ` Clemens Schwaighofer
2004-11-03 1:45 ` Martin Schlemmer [c]
2004-11-03 6:36 ` Clemens Schwaighofer
2004-11-03 17:27 ` Martin Schlemmer [c]
2004-11-02 8:57 ` Christophe Saout
2004-11-02 11:40 ` Jan Knutar
2004-11-02 11:52 ` Christophe Saout [this message]
2004-11-02 12:02 ` Jan Knutar
2004-11-03 1:53 ` Martin Schlemmer [c]
2004-11-03 1:50 ` Martin Schlemmer [c]
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=1099396329.713.4.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=alsa-user@lists.sourceforge.net \
--cc=azarah@nosferatu.za.org \
--cc=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®