mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Knutar <jk-lkml@sci.fi>
To: Christophe Saout <christophe@saout.de>
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 13:40:01 +0200	[thread overview]
Message-ID: <200411021340.03164.jk-lkml@sci.fi> (raw)
In-Reply-To: <1099385872.21422.10.camel@leto.cs.pocnet.net>

On Tuesday 02 November 2004 10:57, Christophe Saout wrote:

> 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.

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.

What's strange is that almost always when it happens, either mplayer or
beep-media-player will have an extra forked process. As bmp is threaded
and I shouldn't see more than one bmp in ps aux on NPTL, this seemed a
bit strange. Strace on the process that looked more recent makes it usually
wake up from deep sleep, and then it promptly vanishes after only a few syscalls.
The strace itself seems to wake it up... After the 'extra' process is gone,
sound output usually resumes, but not always. Other times strace only reveals
the app doing nanosleep's and nothing else, and the only solution is to kill
all apps that might've touched sound.

Another dmix+mplayer issue I have is that mplayer's get_delay for alsa seems
to return bogus values for alsa+dmix case, but I digress...

  reply	other threads:[~2004-11-02 11:40 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 [this message]
2004-11-02 11:52     ` Christophe Saout
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=200411021340.03164.jk-lkml@sci.fi \
    --to=jk-lkml@sci.fi \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=azarah@nosferatu.za.org \
    --cc=christophe@saout.de \
    --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®