Large delay when using realtime priority

Bug #571315 reported by Andrew Agno on 2010-04-28
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jack-audio-connection-kit (Ubuntu)
Undecided
Unassigned

Bug Description

Description: Ubuntu 10.04 LTS
Release: 10.04

$ apt-cache policy jackd
jackd:
  Installed: 0.118+svn3796-1ubuntu2
  Candidate: 0.118+svn3796-1ubuntu2
  Version table:
 *** 0.118+svn3796-1ubuntu2 0
        500 http://mirror.anl.gov/pub/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

I hit a regression after upgrading from Karmic to Lucid using do-release-upgrade -d on April 28. After the upgrade, starting jackd with realtime priority as follows:

% Xvfb :1 -screen 0 1280x1024x8 &
% DISPLAY=:1.0 jackd --verbose -d dummy --rate 44100

causes the following output:

jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

Memory locking is unlimited - this is dangerous. You should probably alter the line:
     @audio - memlock unlimited
in your /etc/limits.conf to read:
     @audio - memlock 3044799
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
SSE2 detected
new client: dummy_pcm, id = 1 type 1 @ 0x1e3d1f0 fd = -1
creating dummy driver ... dummy_pcm|44100|1024|23219|2|2
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now dummy_pcm active ? 1
client dummy_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
21462 waiting for signals
load = 0.0151 max usecs: 7.000, spare = 23212.000
delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...

too many consecutive interrupt delays ... engine pausing
delay of 18446744949882880.000 usecs exceeds estimated spare time of 23212.000; restart ...
cycle execution failure, exiting

DRIVER NT: could not run driver cycle
stopping driver
detaching driver
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
server thread back from poll
start poll on 3 fd's
server thread back from poll
stopping server thread
stopping watchdog thread
last xrun delay: 18446744949882880.000 usecs
max delay reported by backend: 18446744949882880.000 usecs
freeing engine shared memory
max usecs: 7.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'

Using the -r option makes this error go away. This worked in the Karmic release.

Gary M (garym) on 2010-10-16
tags: added: lucid regression-release
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers