On Sun, Mar 24, 2013 at 12:27:47PM +0100, Jan Stary wrote:
> While playing audio, mplayer accasionaly gets stuck with
>
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
> Audio device got stuck!
> A:1036.4 (17:16.3) of 1913.0 (31:53.0) 1.2%
>
>
> It seems some check was introduced into mplayer about a year ago
> http://mplayerhq.hu/pipermail/mplayer-cvslog/2012-February.txt
> whether the audio device times out too much.
>
> I am seeing this more if I simultaneously run firefox,
> or xombrero with many open windows.
>
> Is anybody seeing the same?
> My audio device works fine beside this.
>
> Jan
>
Does this happen with non-MP kernels? If you're using sndiod, you
could try to run:
sudo sndiod -dd <your_options>
and see what happens. This is probably caused by a bug in uaudio.
The new sndiod detects certain anomalies in the device driver and
may display "watchdog timeout" or alike.
-- Alexandre
