Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Pearson <tpearson@raptorengineering.com>
To: alsa-devel@alsa-project.org
Subject: Re: Possible ALSA loopback bug?
Date: Mon, 21 Jan 2019 15:38:19 -0600	[thread overview]
Message-ID: <5C463BCB.2030907@raptorengineering.com> (raw)
In-Reply-To: <5C4519A3.2050200@raptorengineering.com>

On 01/20/2019 07:00 PM, Timothy Pearson wrote:
> I've been running a dedicated machine with ALSA loopback, feeding
> darkice on the capture side and (currently) using mplayer to provide
> audio on the playback side.  I've seen sporadic hangs for a couple of
> years on this setup, but recently with the switch to mplayer I have
> additional information that points more to ALSA than the other applications.
> 
> When the audio hangs, mplayer prints a continuous stream of:
> "Audio device got stuck!"
> 
> The only way to "unstick" the audio stream is to terminate and restart
> mplayer.  Restarting darkice does not fix the stuck stream.  There is no
> pulseaudio on this sytem.
> 
> What would be the next steps to debug this setup?  It's shown up on two
> entirely different installs at this point (Ubuntu 14.04 and Debian 9).
> 
> Thanks!

A bit of additional information:  before audio output ceases entirely,
the messages start printing and the audio becomes very choppy.  The
system has no processes stuck at 100% CPU or any other visible signs of
duress during this time.

Suggestions on debug are welcome!

-- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com

  reply	other threads:[~2019-01-21 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  1:00 Possible ALSA loopback bug? Timothy Pearson
2019-01-21 21:38 ` Timothy Pearson [this message]
2019-01-22 17:13   ` Takashi Iwai
2019-01-22 17:16     ` Timothy Pearson
2019-01-22 17:21       ` Takashi Iwai
2019-01-23 22:02         ` Timothy Pearson

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=5C463BCB.2030907@raptorengineering.com \
    --to=tpearson@raptorengineering.com \
    --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