-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Jarosch wrote: > Hi! > > I've been using the stable 64studio-distro since it's out on a AMD > Athlon64 3000+ without any problems. > Now, I've bought an AMD Athlon64 X2 3800+ dualcore processor and jackd > won't run stable any more. I only changed the CPU, besides this I'm > using the same components with the same 2.6.21-1-multimedia-amd64 kernel > and the same jackd-configuration. When I start jackd, I get this output: > I have a 939 pin 4400+ X2 that works great with that kernel. Stable low latency performance is possible.
> > Everything looks good! But if a actually work with it (for example: > running ardour and jammin), I just have to wait some time and jackd > crashes printing this: > > > jackd watchdog: timeout - killing jackd > 16:51:44.926 Shutdown notification. > 16:51:44.964 Client deactivated. > 16:51:44.969 JACK was stopped successfully. > 16:51:44.972 Post-shutdown script... > 16:51:44.973 killall jackd > zombified - calling shutdown handler > cannot send request type 7 to server > cannot read result for request type 7 from server (Datenübergabe > unterbrochen (broken pipe)) > cannot send request type 7 to server > cannot read result for request type 7 from server (Datenübergabe > unterbrochen (broken pipe)) > jackd: Kein Prozess abgebrochen > 16:51:45.278 Post-shutdown script terminated with exit status=256. > > > After this, it's not possible to start jackd again as long as I'm not > rebooting. (A log out doesn' > t help.) If I want to start jackd without a reboot: > Unlike windows, logging out usually does not accomplish much in Linux. Either; A) jack is still running in the background, in which case running "lsof |grep jack" should find the process. You can then kill it with the kill command. You may need to use the -9 flag. or B) the sound card is not available because it was not released by the jack (this can happen with other apps, like Audacity as well). You did not say what sound card you are using. I am using an RME HDSP 9652 which is using the hdsp kernel module. If this happens to me all that I need to do is: sudo rmmod hdsp && sudo modprobe hdsp Since I started using 64Studio I have not had this problem. I do have it regularly on UbuntuStudio though the hardware is probably the culprit (my 64Studio box has better audio hardware, the Ubuntu box has a crappy integrated audio device). The details will be slightly different depending on your audio device. Your timings are also a little aggressive for an integrated sound device, try increasing your frames per period and or periods per buffer. This will increase your latency but it should also help with stability. Hth, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl7WlkACgkQwRXgH3rKGfOxvQCff6v5klKqgLqfjly4c37cHcXB ECcAoI7bzWaJAZVb0dNH+P98WV7v/0UL =jCQl -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
