Jan Stary [[email protected]] 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.
Appears to be something that will be improved if/when ratchov gets his audio MP lock latency diff in the kernel. You can get the same effect by using GENERIC instead of GENERIC.MP.
