[PlanetCCRMA] Re: [Jackit-devel] cannot connect to jack server - cannot connect to default JACK server
Mark Knecht
mknecht@controlnet.com
Wed Oct 23 15:11:15 2002
Steve & Tim,
The answer still eludes me. In this test I went into BIOS and made sure
all power management was turned off. I then booted and logged in remotely
using ssh, so I've never even touched the mouse or keyboard. X is not
running, although the computer's screen at the console level does black out,
so the xset stuff didn't stick through a reboot. None the less, after about
30-35 minutes jack failed again.
Setiathome was not running, so that's not the problem.
I am struck that the failure came around '8AM'. Could this possibly be
cron related??????? (The clock is wrong. I will reset that...)
Here's the transcript of the most recent tests:
[root@RH73WO root]# jackd -R -d alsa -r 44100 -d Audigy &
[1] 1025
[root@RH73WO root]# 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
[root@RH73WO root]# ps -aux
<SNIP>
root 1025 0.1 0.1 1820 516 pts/0 S 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1026 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1027 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1028 0.2 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1029 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1030 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1031 1.8 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1032 0.0 0.1 2728 760 pts/0 R 07:19 0:00 ps -aux
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# date
Wed Oct 23 07:32:00 PDT 2002
[root@RH73WO root]# date
Wed Oct 23 07:43:43 PDT 2002
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]#
**** alsa_pcm: xrun of at least 0.023 msecs
jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# date
Wed Oct 23 07:51:03 PDT 2002
[root@RH73WO root]# date
Wed Oct 23 07:51:40 PDT 2002
[root@RH73WO root]# jack_lsp
alsa_pcm:in_1
alsa_pcm:in_2
alsa_pcm:out_1
alsa_pcm:out_2
[root@RH73WO root]# jack_lsp
cannot connect to jack server
cannot connect to default JACK server
jack server not running?
[root@RH73WO root]# date
Wed Oct 23 08:02:55 PDT 2002
[root@RH73WO root]# ps -aux
<SNIP>
root 1025 0.0 0.1 1820 516 pts/0 S 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1026 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1027 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1028 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1029 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1030 0.0 7.0 36256 36240 pts/0 SL 07:19 0:01 jackd -R -d
alsa -r 44100 -d Audigy
root 1031 0.0 7.0 36256 36240 pts/0 SL 07:19 0:00 jackd -R -d
alsa -r 44100 -d Audigy
root 1059 0.0 0.1 2728 760 pts/0 R 08:03 0:00 ps -aux
[root@RH73WO root]#
Thanks,
Mark
-----Original Message-----
From: planetccrma-admin@ccrma.Stanford.EDU
[mailto:planetccrma-admin@ccrma.Stanford.EDU]On Behalf Of Mark Knecht
Sent: Wednesday, October 23, 2002 1:14 PM
To: 'PlanetCCRMA (E-mail)'; 'Jackit-List (E-mail)'
Subject: RE: [PlanetCCRMA] Re: [Jackit-devel] cannot connect to jack
server - cannot connect to default JACK server
Steve,
No, actually I know the machine isn't totally 'suspending' when the
monitor turns off since the machine runs setiathome 24 hours a day, and that
continues to process ET data even when the monitor is turned off. It does
make me curious whether setiathome could possibly be the cause of the
problem itself. Setiathome does not make much use of the disk, but uses lots
of CPU cycles. I run it 'niced' so that it gets out of the way (supposedly)
and running it does not cause any xruns, so I hadn't thought much about
removing it. I actually wanted it running to sort of simulate the computer
being very busy but showing that the underlying audio stuff (alsa/jack) is
stable even under a heavier load.
I'm in the process of trying the tests again having done Tim's xset
modification. If that doesn't work, then the next test is BIOS.
Cheers,
Mark
-----Original Message-----
From: planetccrma-admin@ccrma.Stanford.EDU
[mailto:planetccrma-admin@ccrma.Stanford.EDU]On Behalf Of Steve Harris
Sent: Wednesday, October 23, 2002 10:32 AM
To: 'PlanetCCRMA (E-mail)'; 'Jackit-List (E-mail)'
Subject: Re: [PlanetCCRMA] Re: [Jackit-devel] cannot connect to jack
server - cannot connect to default JACK server
On Wed, Oct 23, 2002 at 10:19:14 -0700, Mark Knecht wrote:
> OK, the orange light seems to definitely correspond with when this problem
> starts, and doing things from the remote SSH terminal doesn't change the
> state of the light, so maybe I can try a few things more quickly from
here.
OK, it isn't suspending then, or you wouldn't be able to ssh in.
I'm stumped, I dont see how monitor power managment could affect the sound
system.
- Steve
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA@ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA@ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma