[PlanetCCRMA] RE: [Jackit-devel] cannot connect to jack server - cannot connect to default JACK server
Mark Knecht
mknecht@controlnet.com
Wed Oct 23 08:59:01 2002
Fernando,
First, the problem is repeatable with both jackd and jackstart.
I have a suspicion this might be some sort of power down thing. Please
read at the end.
Last evening, using jackstart to run jack, I let the jack server run
overnight. (Approx. 14 hours.) During that period I got about 30 xruns. This
morning when I came back I attempted jack_lsp before I did anything else on
the machine. jack_lsp said the server wasn't running. ps -aux said it was.
****FIRST XTERM*** (4:30PM Tuesday)
[root@RH73WO root]# jackstart -R -d alsa -r 44100 -d Audigy
jackd 0.39.0
Copyright 2001-2002 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
loading driver ..
creating alsa driver ... Audigy|1024|2|44100|swmon
starting engine
**** alsa_pcm: xrun of at least 0.039 msecs
**** alsa_pcm: xrun of at least 0.025 msecs
**** alsa_pcm: xrun of at least 0.031 msecs
<SNIP>
**** alsa_pcm: xrun of at least 0.037 msecs
**** alsa_pcm: xrun of at least 0.034 msecs
**** alsa_pcm: xrun of at least 0.053 msecs
<IN A SECOND XTERM I ISSUED THE killall COMMAND BELOW>
User defined signal 1
You have new mail in /var/spool/mail/root
[root@RH73WO root]#
[root@RH73WO root]# jack main caught signal 10
engine.c: <-- dump begins -->
client #1: alsa_pcm (type: 1, process? no, fed by 0 clients) start=-1
wait=-1
port #1: alsa_pcm:out_2
port #2: alsa_pcm:out_1
port #3: alsa_pcm:in_2
port #4: alsa_pcm:in_1
engine.c: <-- dump ends -->
***END FIRST XTERM***
***SECOND XTERM*** (6:30AM Wednesday)
<BEFORE THE killall COMMAND ps -aux SAYS THE SERVER IS RUNNING>
[root@RH73WO root]#ps -aux
<SNIP>
root 1896 0.0 0.1 1820 516 pts/2 S Oct22 0:00
jackstart -R -d a
root 1898 0.0 7.0 36256 36240 pts/2 SL Oct22 0:00
jackstart -R -d a
root 1899 0.0 7.0 36256 36240 pts/2 SL Oct22 0:00
jackstart -R -d a
root 1900 0.0 7.0 36256 36240 pts/2 SL Oct22 0:00
jackstart -R -d a
root 1901 0.0 7.0 36256 36240 pts/2 SL Oct22 0:00
jackstart -R -d a
root 1902 0.2 7.0 36256 36240 pts/2 SL Oct22 2:19
jackstart -R -d a
root 1903 0.0 7.0 36256 36240 pts/2 SL Oct22 0:00
jackstart -R -d a
<THE killall COMMAND>
[root@RH73WO root]# killall -v -USR1 jackd
Killed jackd(1896) with signal 10
Killed jackd(1898) with signal 10
Killed jackd(1899) with signal 10
Killed jackd(1900) with signal 10
Killed jackd(1901) with signal 10
Killed jackd(1902) with signal 10
Killed jackd(1903) with signal 10
[root@RH73WO root]#
I then repeated this all again this morning using jackd to start jack and
got the same failure after one hour and three xruns.
One thing that I notice is that there is some sort of power down
happening on this machine. It's an Asus A7V133 set up using RH7.3 and the
Planet. I'm wondering if some sort of sleep thing could easily be causing
this, but I do not know what controls that. On this machine the monitor goes
black after about 15 minutes or so of inactivity. I can wait a few minutes,
wake it up, and check jack with jack_lsp and there are no problems. However,
if I let the machine sleep longer before waking it up, I notice that the
light on this monitor has switched from green to orange, and it takes about
30 seconds after I wiggle the mouse for the screen to warm back up again.
EVERY TIME the machine gets to this state seems to cause a problem for jack!
Now, if the machine is completely going to sleep, I would not be
surprised that jack is possibly having some sort of problem. What controls
this under RH? I'd like to try keeping the machine awake longer and see if
that is what's creating this problem.
Thanks,
Mark
-----Original Message-----
From: jackit-devel-admin@lists.sourceforge.net
[mailto:jackit-devel-admin@lists.sourceforge.net]On Behalf Of Mark
Knecht
Sent: Tuesday, October 22, 2002 5:50 PM
Cc: 'Jackit-List (E-mail)'
Subject: RE: [Jackit-devel] cannot connect to jack server - cannot
connect to default JACK server
We'll see! ;-)
Thanks!
-----Original Message-----
From: jackit-devel-admin@lists.sourceforge.net
[mailto:jackit-devel-admin@lists.sourceforge.net]On Behalf Of Fernando
Pablo Lopez-Lezcano
Sent: Tuesday, October 22, 2002 4:58 PM
To: Mark Knecht
Cc: 'Jackit-List (E-mail)'
Subject: RE: [Jackit-devel] cannot connect to jack server - cannot
connect to default JACK server
> Thanks. I'll try that. It happened again this afternoon, but I had run
> jack in the background using the instructions from the Planet:
>
> jackstart -R -d alsa -r 44100 -d Audigy &
>
> Unfortunately nothing came back to the terminal. I'll run it again nut
leave
> it attached to the terminal where I start it and see if I can catch
> anything.
Hmmm, could it be that the original terminal is no longer around, jack has
nowhere to write error output and just sits there, somewhow blocked in a
write?
-- Fernando
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
_______________________________________________
Jackit-devel mailing list
Jackit-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-devel
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
_______________________________________________
Jackit-devel mailing list
Jackit-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-devel