You changed
nothing but the JACK version?
No: I upgraded by: apt-get upgrade
If you previously installed jack from source over a package, mayhem might be
the result when you upgrade the previously overwritten package. This happened
to me lately, so i thought i'll just shoot in the dark here and mention it :)
Is the tmpdir
reported by "jackd --version" on a tmpfs mount?
jackd --version
jackd version 0.101.1 tmpdir /dev/shm protocol 15
mount
/dev/hda2 on / type reiserfs (rw)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/proc/bus/usb on /proc/bus/usb type usbfs (rw)
/dev/hdb6 on /var/cache/apt/archives type ext3 (rw,nosuid,nodev)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda4 on /mnt/hda4 type fuse (rw,nosuid,nodev,noatime,allow_other)
/dev/hda1 on /mnt/hda1 type ext3 (rw,nosuid,nodev)
/dev/hdb2 on /mnt/hdb2 type reiserfs (rw,nosuid,nodev)
/dev/hdb4 on /mnt/hdb4 type ext3 (rw,nosuid,nodev)
/dev/hdb5 on /mnt/hdb5 type reiserfs (rw,nosuid,nodev)
/dev/hdb7 on /mnt/hdb7 type reiserfs (rw,nosuid,nodev)
/dev/hdb8 on /mnt/hdb8 type ext3 (rw,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
Can you check the RT priorities of the JACK
threads?
How?