Fedora linux forum

00:33:11.502 /usr/bin/jackd -v -R -dalsa -dhw:0 -r48000 -p128 -n2
00:33:11.505 JACK был запущен с PID=7153.
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
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
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
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit
new client: alsa_pcm, id = 1 type 1 @ 0x96df4d8 fd = -1
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
new buffer size 128
registered port system:capture_1, offset = 512
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
7153 waiting for signals
load = 0.4126 max usecs: 22.000, spare = 2644.000
00:33:13.611 Конфигурация сервера сохранена в "/home/volrath/.jackdrc".
00:33:13.613 Перезапуск статистики
00:33:13.683 Клиент активирован
00:33:13.684 Смена соединений JACK.
00:33:13.690 Смена графа соединений JACK.
server thread back from poll
new client: qjackctl, id = 2 type 2 @ 0xb7813000 fd = 14
start poll on 4 fd's
server thread back from poll
new client qjackctl using 15 for events
start poll on 4 fd's
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 2879789233
lock-driven null cycle
back from client event poll after 186 usecs
client qjackctl: wait_fd=9, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
load = 2.5694 max usecs: 126.000, spare = 2540.000
load = 3.0101 max usecs: 92.000, spare = 2574.000
load = 3.9057 max usecs: 128.000, spare = 2538.000
load = 4.4097 max usecs: 131.000, spare = 2535.000
load = 4.3054 max usecs: 112.000, spare = 2554.000
load = 4.4970 max usecs: 125.000, spare = 2541.000
load = 4.6491 max usecs: 128.000, spare = 2538.000
load = 4.6689 max usecs: 125.000, spare = 2541.000
load = 5.2602 max usecs: 156.000, spare = 2510.000
load = 4.6181 max usecs: 106.000, spare = 2560.000
load = 4.5971 max usecs: 122.000, spare = 2544.000
load = 5.2055 max usecs: 155.000, spare = 2511.000
load = 5.1347 max usecs: 135.000, spare = 2531.000
load = 4.8554 max usecs: 122.000, spare = 2544.000
load = 3.5530 max usecs: 60.000, spare = 2606.000
load = 4.1208 max usecs: 125.000, spare = 2541.000
load = 4.3672 max usecs: 123.000, spare = 2543.000
load = 6.3659 max usecs: 223.000, spare = 2443.000
load = 5.5836 max usecs: 128.000, spare = 2538.000
load = 5.0986 max usecs: 123.000, spare = 2543.000
load = 4.9499 max usecs: 128.000, spare = 2538.000
load = 4.9131 max usecs: 130.000, spare = 2536.000
load = 4.8571 max usecs: 128.000, spare = 2538.000
load = 4.9604 max usecs: 135.000, spare = 2531.000
load = 4.8433 max usecs: 126.000, spare = 2540.000
load = 4.1658 max usecs: 93.000, spare = 2573.000
load = 4.6523 max usecs: 137.000, spare = 2529.000
load = 4.7080 max usecs: 127.000, spare = 2539.000
load = 4.7171 max usecs: 126.000, spare = 2540.000
load = 4.7779 max usecs: 129.000, spare = 2537.000
load = 4.7896 max usecs: 128.000, spare = 2538.000
load = 6.1832 max usecs: 202.000, spare = 2464.000
load = 5.4359 max usecs: 125.000, spare = 2541.000
load = 6.0751 max usecs: 179.000, spare = 2487.000
load = 5.4381 max usecs: 128.000, spare = 2538.000
load = 5.0822 max usecs: 126.000, spare = 2540.000
load = 4.2853 max usecs: 93.000, spare = 2573.000
load = 4.5057 max usecs: 126.000, spare = 2540.000
load = 4.6722 max usecs: 129.000, spare = 2537.000
load = 4.7367 max usecs: 128.000, spare = 2538.000
load = 4.7690 max usecs: 128.000, spare = 2538.000
server thread back from poll
new client: jamin, id = 3 type 2 @ 0xb7812000 fd = 17
start poll on 5 fd's
server thread back from poll
new client jamin using 20 for events
start poll on 5 fd's
00:33:57.302 Смена графа соединений JACK.
server thread back from poll
client event poll on 15 for qjackctl starts at 2923409519
back from client event poll after 48 usecs
registered port jamin:in_L, offset = 0
start poll on 5 fd's
server thread back from poll
client event poll on 15 for qjackctl starts at 2923409654
back from client event poll after 8 usecs
registered port jamin:out_L, offset = 1024
start poll on 5 fd's
server thread back from poll
client event poll on 15 for qjackctl starts at 2923409722
back from client event poll after 7 usecs
registered port jamin:in_R, offset = 0
start poll on 5 fd's
server thread back from poll
client event poll on 15 for qjackctl starts at 2923409787
back from client event poll after 7 usecs
registered port jamin:out_R, offset = 1536
start poll on 5 fd's
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
lock-driven null cycle
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 2923443491
back from client event poll after 23 usecs
+++ client is now jamin active ? 1
client jamin: in subgraph after qjackctl, execution_order=1.
client event poll on 20 for jamin starts at 2923443573
back from client event poll after 7 usecs
client qjackctl: wait_fd=16, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 5 fd's
server thread back from poll
connect jamin:out_L and system:playback_1 (output)
client event poll on 20 for jamin starts at 2923443915
back from client event poll after 8 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now jamin active ? 1
client jamin: start_fd=7, execution_order=0.
client event poll on 20 for jamin starts at 2923443991
back from client event poll after 7 usecs
+++ client is now qjackctl active ? 1
client qjackctl: in subgraph after jamin, execution_order=1.
client event poll on 15 for qjackctl starts at 2923444047
back from client event poll after 8 usecs
client jamin: wait_fd=16, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 5 fd's
server thread back from poll
connect jamin:out_R and system:playback_2 (output)
client event poll on 20 for jamin starts at 2923444112
back from client event poll after 14 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 2923444182
back from client event poll after 8 usecs
+++ client is now jamin active ? 1
client jamin: in subgraph after qjackctl, execution_order=1.
client event poll on 20 for jamin starts at 2923444210
back from client event poll after 32 usecs
client qjackctl: wait_fd=16, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 5 fd's
00:33:57.379 Смена соединений JACK.
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
load = 12.7746 max usecs: 554.000, spare = 2112.000
load = 25.0294 max usecs: 994.000, spare = 1672.000
load = 25.7930 max usecs: 708.000, spare = 1958.000
load = 28.5942 max usecs: 837.000, spare = 1829.000
subgraph starting at qjackctl timed out (subgraph_wait_fd=16, status = 0, state = Running, pollret = 0 revents = 0x0)
at 2927416378 waiting on 16 for 3047 usecs, status = 1 sig = 2927413322 awa = 2927413338 fin = 2927413341 dur=19
checking client alsa_pcm: awake at 0 finished at 0
checking client qjackctl: awake at 2927413338 finished at 2927413341
checking client jamin: awake at 0 finished at 0
**** alsa_pcm: <font color="#cc0000">xrun of at least 0.098 msecs</font>
00:34:01.313 XRUN callback (1).
client event poll on 15 for qjackctl starts at 2927420446
back from client event poll after 29 usecs
client event poll on 20 for jamin starts at 2927420492
server thread back from poll
marking client jamin with SOCKET error state = Not triggered errors = 0
trying to lock graph to remove 1 problems
00:34:01.347 Смена графа соединений JACK.
subgraph starting at jamin lost client
bad status (-2) for client jamin handling event (type = 8)
back from client event poll after 31547 usecs
**** alsa_pcm: xrun of at least 16.784 msecs
client event poll on 15 for qjackctl starts at 2927452180
back from client event poll after 29 usecs
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 0
client jamin error status 20000000
removing failed client jamin state = Not triggered errors = 20000000
removing client "jamin"
removing client "jamin" from the processing chain
DIS-connect jamin:out_R and system:playback_2
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now jamin active ? 1
client jamin: start_fd=7, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: in subgraph after jamin, execution_order=1.
client event poll on 15 for qjackctl starts at 2927452386
back from client event poll after 11 usecs
client jamin: wait_fd=16, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
client event poll on 15 for qjackctl starts at 2927452457
back from client event poll after 10 usecs
client event poll on 15 for qjackctl starts at 2927452548
back from client event poll after 10 usecs
DIS-connect jamin:out_L and system:playback_1
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 2927452650
back from client event poll after 9 usecs
+++ client is now jamin active ? 1
client jamin: in subgraph after qjackctl, execution_order=1.
client qjackctl: wait_fd=16, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
client event poll on 15 for qjackctl starts at 2927452723
back from client event poll after 9 usecs
client event poll on 15 for qjackctl starts at 2927454292
back from client event poll after 24 usecs
+++ deactivate jamin
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 2927454537
back from client event poll after 11 usecs
client qjackctl: wait_fd=9, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 1
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 0
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 4 fd's
00:34:01.388 Смена соединений JACK.
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
00:34:01.790 XRUN callback (1 skipped).
load = 16.7540 max usecs: 131.000, spare = 2535.000
load = 10.3087 max usecs: 103.000, spare = 2563.000
load = 7.8175 max usecs: 142.000, spare = 2524.000
00:34:04.750 Клиент деактивирован
00:34:04.750 JACK останавливается ...
server thread back from poll
+++ deactivate qjackctl
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 4 fd's
server thread back from poll
marking client qjackctl with SOCKET error state = Running errors = 0
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 10000000
removing failed client qjackctl state = Running errors = 10000000
removing client "qjackctl"
removing client "qjackctl" from the processing chain
+++ deactivate qjackctl
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 3 fd's
jack main caught signal 15
starting server engine shutdown
stopping driver
server thread back from poll
unloading driver
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 16784.000 usecs
max delay reported by backend: 16784.000 usecs
freeing engine shared memory
max usecs: 994.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
00:34:04.791 Cервер JACK остановлен успешно.
00:34:04.792 Post-shutdown script...
00:34:04.792 killall jackd
jackd: не завеÑ?шён ни один пÑ?оцеÑ�Ñ�
00:34:09.135 Post-shutdown script terminated со статусом выхода 256.