[PlanetCCRMA] FC2.1vP9 - jackstart just quits...

Mark Knecht Mark Knecht <markknecht@gmail.com>
Wed Sep 29 09:35:02 2004


This is a bit strange. I'm still quite uncomfortable with Redhat/FC2
so things are really highly unoptimized. I'll probably send a separate
not with about 10 questions in it later but I'm off to a meeting soon.
This is a Compaq R3070us laptop which runs very well under Gentoo
although I don't have a good low latency kernel there.

I've modprobed realcap allcaps=1 and then try to run jack. It just
dies after about 30 seconds, but there are no messages produced from
the -v option

[mark@flash mark]$ jackstart -R -v -d alsa -r 44100
back from read, ret = 1 errno == Success
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
jackd 0.99.0
Copyright 2001-2003 Paul Davis 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

JACK compiled with System V SHM support
registered builtin port type 32 bit float mono audio
capabilities: = cap_setpcap,cap_ipc_lock,cap_sys_nice,cap_sys_resource+eip
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x8058890 fd = -1
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
new buffer size 1024
-- jack_rechain_graph()
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
5319 waiting for signals
jackd watchdog: timeout - killing jackd
Aborted
[mark@flash mark]$

If I execute the same command but wiggle my USB mouse then things get
more interesting:

[mark@flash mark]$ jackstart -R -v -d alsa -r 44100
back from read, ret = 1 errno == Success
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
jackd 0.99.0
Copyright 2001-2003 Paul Davis 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

registered builtin port type 32 bit float mono audio
capabilities: = cap_setpcap,cap_ipc_lock,cap_sys_nice,cap_sys_resource+eip
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x8058890 fd = -1
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
new buffer size 1024
-- jack_rechain_graph()
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
5326 waiting for signals
load = 0.0258 max usecs: 12.000, spare = 23207.000
load = 0.0388 max usecs: 12.000, spare = 23207.000
load = 0.0431 max usecs: 11.000, spare = 23208.000
load = 0.0517 max usecs: 14.000, spare = 23205.000
load = 0.0538 max usecs: 13.000, spare = 23206.000
load = 0.0549 max usecs: 13.000, spare = 23206.000
load = 0.0641 max usecs: 17.000, spare = 23202.000
delay of 64785.000 usecs exceeds estimated spare time of 23202.000; restart ...
load = 0.0686 max usecs: 17.000, spare = 23202.000
load = 0.0623 max usecs: 13.000, spare = 23206.000
load = 0.0635 max usecs: 15.000, spare = 23204.000
load = 0.0597 max usecs: 13.000, spare = 23206.000
load = 0.0622 max usecs: 15.000, spare = 23204.000
load = 0.0677 max usecs: 17.000, spare = 23202.000
load = 0.0640 max usecs: 14.000, spare = 23205.000
load = 0.0621 max usecs: 14.000, spare = 23205.000  <---stopped wiggling
jackd watchdog: timeout - killing jackd
Killed
[mark@flash mark]$

Now, there are a huge number of processes running. I've seen artsd
start a couple of times and block Jack. I have much to do to give KDE
a chance, I think, but I do not know what to think of this operation.

I did set the THREADED option to 0 as per the setup email. Seems like
possibly that's not a good idea? Not sure at all.

What info can I provide to help understand this better?

Cheers,
Mark