JACK problem has me re-booting more often than Windows

  • aka_guitarist
Posted: Sun, 10/28/2007 - 03:54
When JACK crashes (which is VERY often) it won't restart unless I reboot the computer. I downloaded the image for 64Studio live version, then downloaded the installation DVD and installed from that. According to the update manager, there are no new packages to load to update anything. My hardware: Gigabyte GA-7ZX motherboard AMD Duron (I think a 900 or 950 Mhz) 512 MB RAM NVidia Graphics card On Board Creative sound PCI sound card SB24 Live 200 GB WD EIDE hard drive (master) 120 GB Maxtor hard drive (slave) Here are two JACK message dumps the first is a successful start after a reboot (verbose output is on): **************** start of paste ****************** 3:58:00.338 Patchbay deactivated. 03:58:00.644 Statistics reset. 03:58:01.263 MIDI connection graph change. JACK tmpdir identified as [/dev/shm] 03:58:01.317 MIDI connection change. 03:58:12.895 Startup script... 03:58:12.897 artsshell -q terminate JACK tmpdir identified as [/dev/shm] can't create mcop directory Link points to "/tmp/ksocket-admin007" 03:58:13.667 Startup script terminated with exit status=256. 03:58:13.672 JACK is starting... 03:58:13.674 /usr/bin/jackd -v -R -dalsa -dhw:0 -r48000 -p256 -n2 03:58:13.688 JACK was started with PID=4440 (0x1158). getting driver descriptor from /usr/lib/jack/jack_freebob.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_dummy.so jackd 0.103.0 Copyright 2001-2005 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. 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 .. apparent rate = 48000 creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 new client: alsa_pcm, id = 1 type 1 @ 0x8059008 fd = -1 configuring for 48000Hz, period = 256 frames, buffer = 2 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 2 periods for playback new buffer size 256 registered port alsa_pcm:capture_1, offset = 1024 registered port alsa_pcm:capture_2, offset = 2048 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. -- jack_rechain_graph() 4440 waiting for signals load = 0.3938 max usecs: 42.000, spare = 5291.000 03:58:15.990 Server configuration saved to "/home/admin007/.jackdrc". 03:58:16.001 Statistics reset. 03:58:16.193 Client activated. 03:58:16.212 Audio connection change. 03:58:16.267 Audio connection graph change. new client: qjackctl-4433, id = 2 type 2 @ 0xb6ba5000 fd = 15 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client qjackctl-4433: start_fd=5, execution_order=0. client qjackctl-4433: wait_fd=10, execution_order=1 (last client). -- jack_rechain_graph() JACK tmpdir identified as [/dev/shm] load = 1.4626 max usecs: 135.000, spare = 5198.000 load = 2.0626 max usecs: 142.000, spare = 5191.000 load = 2.1845 max usecs: 123.000, spare = 5210.000 load = 2.8455 max usecs: 187.000, spare = 5146.000 **************** end of paste ****************** at that point it continues to stream messages and seems to work fine until... something I'm trying to get to work (Rosegarden most recently) causes JACK to die, at which point I have to reboot the computer or JACK won't sucessfully start. (JACK is killed shortly after starting.) The output looks like this: **************** start of paste ****************** 03:47:00.614 Patchbay deactivated. 03:47:00.830 Statistics reset. JACK tmpdir identified as [/dev/shm] 03:47:01.321 MIDI connection graph change. 03:47:01.369 MIDI connection change. 03:47:02.713 Startup script... 03:47:02.714 artsshell -q terminate JACK tmpdir identified as [/dev/shm] 03:47:03.207 Startup script terminated with exit status=256. 03:47:03.209 JACK is starting... 03:47:03.209 /usr/bin/jackd -v -R -dalsa -dhw:0 -r48000 -p256 -n2 03:47:03.217 JACK was started with PID=5766 (0x1686). getting driver descriptor from /usr/lib/jack/jack_freebob.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_dummy.so jackd 0.103.0 Copyright 2001-2005 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. 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 .. apparent rate = 48000 creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 new client: alsa_pcm, id = 1 type 1 @ 0x8059008 fd = -1 configuring for 48000Hz, period = 256 frames, buffer = 2 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 2 periods for playback new buffer size 256 registered port alsa_pcm:capture_1, offset = 1024 registered port alsa_pcm:capture_2, offset = 2048 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. -- jack_rechain_graph() 5766 waiting for signals 03:47:05.282 Server configuration saved to "/home/admin007/.jackdrc". 03:47:05.288 Statistics reset. 03:47:05.352 Client activated. 03:47:05.375 Audio connection change. 03:47:05.401 Audio connection graph change. 03:47:05.410 XRUN callback (1). JACK tmpdir identified as [/dev/shm] new client: qjackctl-5761, id = 2 type 2 @ 0xb6b35000 fd = 15 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client qjackctl-5761: start_fd=5, execution_order=0. client qjackctl-5761: wait_fd=10, execution_order=1 (last client). -- jack_rechain_graph() 03:47:07.407 XRUN callback (204 skipped). jackd watchdog: timeout - killing jackd zombified - calling shutdown handler 03:47:08.430 Shutdown notification. 03:47:08.431 Client deactivated. 03:47:08.437 JACK was stopped successfully. 03:47:08.438 Post-shutdown script... 03:47:08.439 killall jackd cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) jackd: no process killed 03:47:08.678 Post-shutdown script terminated with exit status=256. **************** end of paste ****************** At that point, IF I REBOOT the machine JACK will start and work. I've tried using "/etc/init.d/alsa force-reload" to see if that would accomplish the same thing as a reboot, but no joy. I've searched everyplace I could think of to find the "stop/start" commands for alsa, etc. (assuming that is even the problem.) the alsa package version: 64studio:/home/admin007# dpkg -l |grep alsa ii alsa-base 1.0.14-1~bpo.1 ALSA driver configuration files ii alsa-firmware 1.0.14-1~bpo.1 Firmware binaries for the soundcards support ii alsa-firmware-loaders 1.0.13-1 ALSA software loaders for specific hardware ii alsa-modules-2.6.21-1-multimedia-486 1.0.14-1~bpo.1+2.6.21-2 ALSA modules for kernel 2.6.21-1-multimedia- ii alsa-oss 1.0.12-1 ALSA wrapper for OSS applications ii alsa-source 1.0.14-1~bpo.1 ALSA driver sources ii alsa-tools 1.0.13-1 Console based ALSA utilities for specific ha ii alsa-tools-gui 1.0.13-1 GUI based ALSA utilities for specific hardwa ii alsa-utils 1.0.13-2 ALSA utilities ii gstreamer0.10-alsa 0.10.10-4 GStreamer plugin for ALSA ii libclalsadrv1 1.2.2-1~bpo.1 ALSA driver C++ access library ii libpt-plugins-alsa 1.10.2-2 Portable Windows Library Audio Plugin for th more system info: 64studio:/home/admin007# lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:0a.0 Multimedia audio controller: Creative Labs SB Audigy LS 00:0c.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 00:0c.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 00:0c.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 00:0c.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) 00:0c.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 Controller 00:0d.0 Ethernet controller: Macronix, Inc. [MXIC] MX987x5 (rev 25) 00:0e.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) 00:0f.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 23) 01:00.0 VGA compatible controller: nVidia Corporation NV15 [GeForce2 GTS/Pro] (rev a4) So... is there something I can do to at least not have to reboot everytime I cause JACK to crash? That, obiviously, would save me a lot of time. Thanks.

jack problem. ?

  • ttoine
  • 11/15/07
  • Wed, 03/19/2008 - 18:28
Wich sample frequency do you ant to work with ? I mean, your configuration is bit light if you really want to work at 96khz.... and so, the system can not handle to much application and audio tracks. And of course it is more difficult if you want to work at low latency. With a M-Audio Audiophile 2496, it appends to me with the same configuration to freeze the system and to have to restart. Toine

Thanks Quentin; I'd also

  • ejoftheweb
  • 03/17/08
  • Mon, 03/17/2008 - 20:43
Thanks Quentin; I'd also found that thread which funnily enough I'd followed a few weeks back trying to get a mate's Tascam working... but unfortunately it has no answers to the Jack problem, just three more people in the same boat. The only clue is that the others seem to be having the problem with different sound cards, but that doesn't get very far because the envy24/ice1712 driver should be mature enough by now so Alsa isn't my prime suspect. I think I'll try upgrading to jackd 0.109 to see what happens.

Would this help...

  • Quentin Harley
  • 05/24/07
  • Mon, 03/17/2008 - 20:26
http://ubuntuforums.org/showthread.php?t=431066&page=4 I searched for the tell-tale "DRIVER NT: could not run driver cycle" line and got to this page eventually. I do not know the exact steps for your current hardware, but this could point you in the right direction...

same problem - not solved...

  • ejoftheweb
  • 03/17/08
  • Mon, 03/17/2008 - 19:32
I have just installed 64Studio on a brand-new, purpose-built system to function as a DAW (but using an Envy24/ICE1712-based Terratec DMX6Fire from another machine). Jack is so unstable as to be unusable. Following this thread I have disabled the onboard sound but to no avail: Jack starts, makes sound, then crashes. The key lines in the Jack messages seem to be these: DRIVER NT: could not run driver cycle jack main caught signal 12 19:23:39.070 Shutdown notification. 19:23:39.070 Client deactivated. 19:23:39.071 JACK is stopping... starting server engine shutdown stopping driver

Config

  • Quentin Harley
  • 05/24/07
  • Fri, 02/08/2008 - 16:39
If you follow the FAQ about the device order (now point 11) You just don't configure the on board sound, and it should be gone. If not, configure it as device -2, and it should be gone. Cheers!

I have a simialr set up with

  • arjayiii
  • 01/30/08
  • Fri, 02/08/2008 - 12:44
I have a simialr set up with SB audigy and an on board sound card , frankly I'd stick to using the good quality card and disable th onboard sound in the bios . Sometimes however the system will still recognise the on baord chip even if it is disabled in the bios ! Just run alsaconf to configure the correct card , ( which for a while I had to do every time I started the system but recent updates to studio64 seem to have fixed it ) Rick

Soundcards and conflicting IRQ's

  • porisija
  • 09/29/07
  • Thu, 02/07/2008 - 18:39
In my experiments with different soundcards and various setups I have noticed that dual setups are very, very difficult. Both your cards are Creative's products - alsaconf is actually quite good at recognising chipsets. But I believe changing your SB Live cards PCI -buss setup will help you. Your cards might be sharing an interrupt (IRQ) because ensoniq chipset is identifying itself as a PCI device. This leads to jack locking up. Alas.. Open up your computer case and change your SB-Live card to some other PCI buss on the motherboard, boot up and see what happens. Disabling the onboard chipset in BIOS is in my opinion a good idea - most onboard sound chipsets are "not-too-good" when compared to separate devices. Your SB Live card is quite good and you probably do not need a dual card setup. Check this: http://www.ibm.com/developerworks/library/l-hw2.html and possibly these: http://www.linuxjournal.com/node/1000262 http://www.gentoo.org/doc/en/articles/hardware-stability-p2.xml

perhaps a udev problem..?

  • porisija
  • 09/29/07
  • Sun, 10/28/2007 - 17:30
Your lspci -command shows you have two soundcards in your system, but is your kernel/jackd configured to use them properly? Maybe this will help: http://alsa.opensrc.org/index.php/MultipleCards#Multiple_devices Both soundcards are well supported by alsa, so I suspect a configuration problem.. Anyways, two soundcards..? You may need to setup your BIOS too

Re: perhaps a udev problem..?

  • aka_guitarist
  • 10/16/07
  • Sun, 10/28/2007 - 22:06
Thanks for the response, Porisija. The two soundcards are the motherboard-based one and the SB-24 Live PCI card. The descriptions seem odd, it refers to a SB Audigy. excerpts from lspci output: 00:0a.0 Multimedia audio controller: Creative Labs SB Audigy LS 00:0e.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) What is strange is that the Mother board manual says the on-board sound is a Creative CT5880 (optional). I guess the standard sound is a AC'97 CODEC. This is the sound cards that it finds when I do alsaconf: ens1371 Ensoniq 5880 AudioPCI (rev 02) ca0106 Creative Labs SB Audigy LS The second one is what the box says is a SB-24 Live. It took a ton of trial and error to get that straight. As far as the order of loading the alsa modules, that was a huge stumbling block. I put the following at the end of the /etc/modprobe.d/alsa-base file: (per FAQ #10) # Added aliases per 64Studio forum FAQ 10 # SB 24-Live card is snd-card-0 and onboard Creative is snd-card-1 others not defined alias snd-card-0 snd-sb0410 options snd-sb0410 index=0 alias snd-card-1 snd-ens1371 options snd-ens1371 index=1 It seemed to help enormously. JACK, Adour, and Hydrogen were working for basic things using the higher-quality sound card. I'm studying the link you posted. I agree with you that there is likely some sort of config issue, but not sure how to find it. I did try dis-abling the onboard sound in the BIOS, but it didn't seem to help. So I'm stuck for now. But thanks again for the response. I'll study that info at your link a little longer.