25 Jun
2010
25 Jun
'10
3:55 p.m.
Hi there
I have a problem with jack. I have a Edirol fa-101 firewire soundcard on amd
processer (2500+) with 512Mb RAM. If i have low frames/period setting ( 128)
jack shots down after short time (2 - 20 sec or almost instantly if I run a
program; ardour or openoffice) or if I have a high frames/period setting
(1024) I get xruns.
I have tried almost every setting possible and tried changing nice values on
the firewire card and a lot of other stuff.
Can anyone help?
Kind Regards Thomas
Here is a uname -a
Linux thomas-laptop 2.6.31-10-rt #153-Ubuntu SMP PREEMPT RT Tue Jan 12
10:42:21 UTC 2010 i686 GNU/Linux
thomas@thomas-laptop:~$ cat .jackdrc
/usr/bin/jackd -P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
First jack messages when framesperiod is 128:
13:32:19.478 Patchbay deactivated.
13:32:19.503 Statistics reset.
13:32:19.713 ALSA connection graph change.
13:32:20.223 ALSA connection change.
13:33:28.994 Startup script...
13:33:28.996 artsshell -q terminate
sh: artsshell: not found
13:33:29.400 Startup script terminated with exit status=32512.
13:33:29.401 JACK is starting...
13:33:29.402 /usr/bin/jackd -P82 -t2000 -m -dfirewire -r44100 -p128 -n3
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 427074
13:33:29.436 JACK was started with PID=5101.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
libffado 2.0.0 built Mar 31 2010 14:47:42
13:33:31.527 Server configuration saved to "/home/thomas/.jackdrc".
13:33:31.531 Statistics reset.
13:33:31.534 Client activated.
13:33:31.537 JACK connection change.
13:33:31.552 JACK connection graph change.
firewire ERR: wait status < 0! (= -1)
DRIVER NT: could not run driver cycle
13:33:45.166 JACK connection graph change.
13:33:45.251 JACK connection change.
jack main caught signal 12
no message buffer overruns
zombified - calling shutdown handler
13:33:45.334 Shutdown notification.
13:33:45.337 JACK is stopping...
13:33:45.338 JACK is being forced...
13:33:45.539 JACK was stopped successfully.
13:33:45.540 Post-shutdown script...
13:33:45.541 killall jackd
jackd: no process found
13:33:45.958 Post-shutdown script terminated with exit status=256.
Second when framesperiod is 1024:
13:35:54.240 Patchbay deactivated.
13:35:54.259 Statistics reset.
13:35:54.375 ALSA connection graph change.
13:35:54.762 ALSA connection change.
13:37:02.730 Startup script...
13:37:02.731 artsshell -q terminate
sh: artsshell: not found
13:37:03.137 Startup script terminated with exit status=32512.
13:37:03.138 JACK is starting...
13:37:03.139 /usr/bin/jackd -P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 427074
13:37:03.176 JACK was started with PID=5140.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
libffado 2.0.0 built Mar 31 2010 14:47:42
13:37:05.304 Server configuration saved to "/home/thomas/.jackdrc".
13:37:05.319 Statistics reset.
13:37:05.346 Client activated.
13:37:05.373 JACK connection graph change.
13:37:06.047 JACK connection graph change.
13:37:06.240 JACK connection change.
13:37:09.708 XRUN callback (1).
13:37:15.710 XRUN callback (2).
13:37:45.718 XRUN callback (3).
13:38:09.713 XRUN callback (4).
13:38:15.718 XRUN callback (5).
13:38:39.713 XRUN callback (6).
13:38:45.716 XRUN callback (7).
13:39:09.711 XRUN callback (8).
13:39:15.714 XRUN callback (9).
13:39:39.713 XRUN callback (10).
13:39:45.714 XRUN callback (11).
13:40:09.711 XRUN callback (12).
13:40:15.713 XRUN callback (13).
13:40:45.722 XRUN callback (14).
13:41:09.715 XRUN callback (15).
13:41:15.720 XRUN callback (16).
13:41:45.707 XRUN callback (17).
thomas@thomas-laptop:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : Mobile AMD Athlon(tm) XP 2500+
stepping : 0
cpu MHz : 1855.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat
pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow up
bogomips : 3710.02
clflush size : 32
power management: ts fid vid
Here is cat/proc interrupts CPU0
0: 7412489 XT-PIC-XT timer
1: 5159 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 1 XT-PIC-XT
4: 1 XT-PIC-XT
5: 1 XT-PIC-XT
6: 1 XT-PIC-XT
7: 1 XT-PIC-XT
8: 0 XT-PIC-XT rtc0
9: 1969 XT-PIC-XT acpi
10: 445734 XT-PIC-XT ohci1394, yenta, radeon@pci:0000:01:05.0
11: 32807 XT-PIC-XT ehci_hcd:usb1, ohci_hcd:usb2,
ohci_hcd:usb3, eth0, ALI 5451
12: 292660 XT-PIC-XT i8042
14: 35966 XT-PIC-XT pata_ali
15: 111856 XT-PIC-XT pata_ali
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
SPU: 0 Spurious interrupts
CNT: 0 Performance counter interrupts
PND: 0 Performance pending work
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 25 Machine check polls
ERR: 0
MIS: 0
*
My Firewire card:*
thomas@thomas-laptop:~$ lspci | grep Fire
00:0a.1 FireWire (IEEE 1394): Texas Instruments PCI4410 FireWire Controller
(rev 02)
*Htop:*
RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0
13 root RT -5 0 0 0 S 0.0 0.0 0:00.00 posixcputmr/0
14 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
4565 thomas -93 0 89936 8016 6000 S 0.0 1.4 0:00.00 /usr/bin/jackd
-P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
643 root -91 -5 0 0 0 S 0.0 0.0 0:00.00 irq/8-rtc0
4562 thomas -84 0 89936 8016 6000 S 7.0 1.4 0:04.03 /usr/bin/jackd
-P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
4566 thomas -83 0 89936 8016 6000 S 1.0 1.4 0:00.84 /usr/bin/jackd
-P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
4563 thomas -82 0 89936 8016 6000 S 6.0 1.4 0:03.65 /usr/bin/jackd
-P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
603 root -81 -5 0 0 0 S 0.0 0.0 0:00.00
irq/11-ehci_hcd
608 root -81 -5 0 0 0 S 0.0 0.0 0:00.00
irq/11-ohci_hcd
612 root -80 -5 0 0 0 S 0.0 0.0 0:00.00
irq/11-ohci_hcd
4570 thomas -78 0 68688 22936 17744 S 0.0 4.0 0:00.19
/usr/bin/qjackctl.bin
629 root -76 -5 0 0 0 S 0.0 0.0 0:00.03 irq/1-i8042
628 root -75 -5 0 0 0 S 0.0 0.0 0:01.00 irq/12-i8042
517 root -51 -5 0 0 0 S 0.0 0.0 0:00.04
irq/14-pata_ali
518 root -51 -5 0 0 0 S 0.0 0.0 0:00.09
irq/15-pata_ali
187 root -51 -5 0 0 0 S 0.0 0.0 0:00.00 irq/9-acpi
853 root -51 -5 0 0 0 S 0.0 0.0 0:00.42
irq/10-ohci1394
3571 root -51 -5 0 0 0 S 0.0 0.0 0:00.31 irq/10-yenta
3648 root -51 -5 0 0 0 S 0.0 0.0 0:00.00 irq/11-ALI
5451
3708 root -51 -5 0 0 0 S 0.0 0.0 0:00.00 irq/11-eth0
4091 root -51 -5 0 0 0 S 0.0 0.0 0:00.22
irq/10-radeon@p
5 root -50 -5 0 0 0 S 0.0 0.0 0:01.52 sirq-timer/0
8 root -50 -5 0 0 0 S 0.0 0.0 0:00.26 sirq-block/0
12 root -50 -5 0 0 0 S 0.0 0.0 0:00.22 sirq-rcu/0
4 root -50 -5 0 0 0 S 0.0 0.0 0:00.00 sirq-high/0
6 root -50 -5 0 0 0 S 0.0 0.0 0:00.00 sirq-net-tx/0
7 root -50 -5 0 0 0 S 0.0 0.0 0:00.00 sirq-net-rx/0
9 root -50 -5 0 0 0 S 3.0 0.0 0:01.81 sirq-tasklet/0
10 root -50 -5 0 0 0 S 0.0 0.0 0:00.00 sirq-sched/0
11 root -50 -5 0 0 0 S 0.0 0.0 0:00.00 sirq-hrtimer/0
17 root -2 -5 0 0 0 S 0.0 0.0 0:00.06 events/0
4561 thomas -2 0 89936 8016 6000 S 0.0 1.4 0:00.00 /usr/bin/jackd
-P82 -t2000 -m -dfirewire -r44100 -p1024 -n3
25 Jun
25 Jun
4:15 p.m.
Hi!
I don't know how much it might help with the xruns, but the shutting down
part might be better with the timeout option:
jackd -R --timeout 4500 ...
I hope tat helps.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
6:52 p.m.
How do I do that?
2010/6/25 Julien Claassen <julien(a)c-lab.de>
Hi!
I don't know how much it might help with the xruns, but the shutting down
part might be better with the timeout option:
jackd -R --timeout 4500 ...
I hope tat helps.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
6:54 p.m.
Sorry forgot this:
2010/6/25 Julien Claassen <julien(a)c-lab.de>
Hi!
How do I do that?
I don't know how much it might help with the
xruns, but the shutting down
part might be better with the timeout option:
jackd -R --timeout 4500 ...
I hope tat helps.
Kindest regards
Julien
6:58 p.m.
On 2010-06-25 18:52, Thomas Hedegaard wrote:
How do I do that?
By typing 4500 in the box qjackctl->setup->Timeout(ms)...
--
Atte
http://atte.dk http://modlys.dk
7:02 p.m.
I can set it to 5000 but that didnt change anything...
2010/6/25 Atte André Jensen <atte(a)email.dk>
On 2010-06-25 18:52, Thomas Hedegaard wrote:
How do I do that?
By typing 4500 in the box qjackctl->setup->Timeout(ms)...
--
Atte
http://atte.dk http://modlys.dk
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
7:05 p.m.
Hi Thomas!
God knows why, but I tried 5000 as well once, but faired best with 4500.
But still if it doesn't work, I suppose it's something ese. this onlyhelps,
when starting larger audio apps, that take a little time to get loaded.
LinuxSampler used to crash my JACK without that, so might Ardour in theory.
It's just a precaution. You might store that setting anyway.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
26 Jun
26 Jun
8:37 a.m.
*God knows why, but I tried 5000 as well once, but faired best with 4500.
But still if it doesn't work, I suppose it's something ese. this onlyhelps,
when starting larger audio apps, that take a little time to get loaded.
LinuxSampler used to crash my JACK without that, so might Ardour in theory.
It's just a precaution. You might store that setting anyway.
*No such luck Im afraid*. *I changed the v alue but nothing really
happened..
Best Thomas
2010/6/25 Julien Claassen <julien(a)c-lab.de>
Hi Thomas!
God knows why, but I tried 5000 as well once, but faired best with 4500.
But still if it doesn't work, I suppose it's something ese. this onlyhelps,
when starting larger audio apps, that take a little time to get loaded.
LinuxSampler used to crash my JACK without that, so might Ardour in theory.
It's just a precaution. You might store that setting anyway.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
25 Jun
25 Jun
4:19 p.m.
On 06/25/2010 03:55 PM, Thomas Hedegaard wrote:
firewire ERR: wait status < 0! (= -1)
DRIVER NT: could not run driver cycle
Hello Thomas,
This could indicate something is blocking the data stream, in your case
maybe the Radeon card. Are you using rtirq-init? If not it may be wise
to give it a try: http://ubuntuforums.org/showthread.php?t=1328175 and
http://subversion.ffado.org/wiki/IrqPriorities
I would also set JACK's prio lower, maybe 70 would be better. And
Firewire cards, in my personal experience, work better with a periods
setting of 2 instead of 3.
Best,
Jeremy
6:15 p.m.
On Fri, Jun 25, 2010 at 6:55 AM, Thomas Hedegaard <thomas(a)vector.dk> wrote:
/usr/bin/jackd -P82 -t2000 -m -dfirewire -r44100
-p1024 -n3
...
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 427074
What about taking care of the above problem?
If some other program is competing against jackd for memory, and
you're allowing unlimited memory locking, perhaps that's a potential
source of problems?
-- Niels
http://nielsmayer.com
6:49 p.m.
On 2010-06-25 18:15, Niels Mayer wrote:
What about taking care of the above problem?
If some other program is competing against jackd for memory, and
you're allowing unlimited memory locking, perhaps that's a potential
source of problems?
Good catch! It's been a long time since I ran with 512MB ram, but that
could be a problem...
--
Atte
http://atte.dk http://modlys.dk
6:53 p.m.
On Fri, Jun 25, 2010 at 12:49 PM, Atte André Jensen <atte(a)email.dk> wrote:
On 2010-06-25 18:15, Niels Mayer wrote:
no, its not the problem.
the warning is really a bit of overkill.
What about taking care of the above problem?
If some other program is competing against jackd for memory, and
you're allowing unlimited memory locking, perhaps that's a potential
source of problems?
Good catch! It's been a long time since I ran with 512MB ram, but that could
be a problem...
6:56 p.m.
On 2010-06-25 18:53, Paul Davis wrote:
no, its not the problem.
the warning is really a bit of overkill.
Ok, thanks for clearing that up. So "@audio - memlock unlimited" is not
to be considered "dangerous" after all?
--
Atte
http://atte.dk http://modlys.dk
9:03 p.m.
Hi,
On Friday 25 June 2010 15:55:06 Thomas Hedegaard wrote:
I have a problem with jack. I have a Edirol fa-101
firewire soundcard on
amd processer (2500+) with 512Mb RAM. If i have low frames/period setting
( 128) jack shots down after short time (2 - 20 sec or almost instantly if
I run a program; ardour or openoffice) or if I have a high frames/period
setting (1024) I get xruns.
I have tried almost every setting possible and tried changing nice values
on the firewire card and a lot of other stuff.
Changing nice-values will not help because:
10: 445734 XT-PIC-XT ohci1394, yenta,
radeon@pci:0000:01:05.0
...your firewire-controller shares its interrupt with the graphics card. That
will almost always make problems.
And using a pccard won't help you, as your pccard-slot shares that same
interrupt as well. Bummer.
It might be that your BIOS allows selecting interrupts for devices. Other then
that I fear you are completely out-of-luck with that laptop for firewire-audio.
My Firewire card:*
thomas@thomas-laptop:~$ lspci | grep Fire
00:0a.1 FireWire (IEEE 1394): Texas Instruments PCI4410 FireWire Controller
(rev 02)
I think that one should work (if it wasn't sharing the interrupt).
A side-note: There is a reason the ffado-README contains instructions what to
report in case of errors. Mostly a verbose log of jack. And the output of
ffado-diag...
Have fun,
Arnold
26 Jun
26 Jun
8:30 a.m.
*It might be that your BIOS allows selecting interrupts for devices. Other
then
that I fear you are completely out-of-luck with that laptop for
firewire-audio.*
I cant change my interrupts in BIOS unfortunately . But when I run Win xp on
this computer I can record four tracks simultaneously with 10ms latency or
mix 8 tracks with plugins. So this should not be a hardware issue.
*A side-note: There is a reason the ffado-README contains instructions what
to
report in case of errors. Mostly a verbose log of jack. And the output of
ffado-diag...*
This last bit I dont understand..
Thanks for your help
Thomas
2010/6/25 Arnold Krille <arnold(a)arnoldarts.de>
Hi,
On Friday 25 June 2010 15:55:06 Thomas Hedegaard wrote:
I have a problem with jack. I have a Edirol
fa-101 firewire soundcard on
amd processer (2500+) with 512Mb RAM. If i have low frames/period setting
( 128) jack shots down after short time (2 - 20 sec or almost instantly
if
I run a program; ardour or openoffice) or if I
have a high frames/period
setting (1024) I get xruns.
I have tried almost every setting possible and tried changing nice values
on the firewire card and a lot of other stuff.
Changing nice-values will not help because:
10: 445734 XT-PIC-XT ohci1394,
yenta,
radeon@pci:0000:01:05.0
...your firewire-controller shares its interrupt with the graphics card.
That
will almost always make problems.
And using a pccard won't help you, as your pccard-slot shares that same
interrupt as well. Bummer.
It might be that your BIOS allows selecting interrupts for devices. Other
then
that I fear you are completely out-of-luck with that laptop for
firewire-audio.
My Firewire card:*
thomas@thomas-laptop:~$ lspci | grep Fire
00:0a.1 FireWire (IEEE 1394): Texas Instruments PCI4410 FireWire
Controller
(rev 02)
I think that one should work (if it wasn't sharing the interrupt).
A side-note: There is a reason the ffado-README contains instructions what
to
report in case of errors. Mostly a verbose log of jack. And the output of
ffado-diag...
Have fun,
Arnold
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
8:56 a.m.
Hi,
On Saturday 26 June 2010 08:30:36 Thomas Hedegaard wrote:
*It might be that your BIOS allows selecting
interrupts for devices. Other
then
that I fear you are completely out-of-luck with that laptop for
firewire-audio.*
I cant change my interrupts in BIOS unfortunately . But when I run Win xp
on this computer I can record four tracks simultaneously with 10ms latency
or mix 8 tracks with plugins. So this should not be a hardware issue.
And I have ffado together with nvidia graphics (without sharing interrupts)
working. So its not a software issue.
Now what?
Believe me: Sharing interrupts is still a bad problem in this century. At
least when you have to interrupt-heavy devices like firewire and graphics share
the IRQ.
And its not that re-assuring that the other operating system works: There you
have a special driver that works around the hardware quirks. And if you look
at your sound-devices documentation, they will tell you a long list of
probably-not-working controllers and only a small list of working ones.
*A side-note: There is a reason the ffado-README
contains instructions what
to
report in case of errors. Mostly a verbose log of jack. And the output of
ffado-diag...*
This last bit I dont understand..
What it says, is that ffado (the bit of software you use to make jackd talk
firewire) has an extensive README-file which explains what to do in case you
need help or want to report a bug. Because most people (you too!) miss to get
us all the information we devs need. And we feel that our spare-time is better
spent hacking and fixing then telling people the same things over and over
again. Thats why you really should read the README-files of apps/libraries.
Have fun,
Arnold
PS: Your style of citations is broken and a strange mix of TOFU and
citations...
4:08 p.m.
Hi Arnold
As you can see from my first post I suspected the interrupt issue to be the
matter here all along. I was just wondering why I could make it work in win
xp and not in ubuntu.
I will try if theres a BIOS update or something that makes it possible to
change interrupts
I was not aware that ffado has a readme-file. I will read that
Best Thomas
On Saturday 26 June 2010 08:30:36 Thomas Hedegaard wrote:
*It might be that your BIOS allows selecting
interrupts for devices.
Other
then
that I fear you are completely out-of-luck with that laptop for
firewire-audio.*
I cant change my interrupts in BIOS unfortunately . But when I run Win xp
on this computer I can record four tracks simultaneously with 10ms
latency
or mix 8 tracks with plugins. So this should not
be a hardware issue.
And I have ffado together with nvidia graphics (without sharing interrupts)
working. So its not a software issue.
Now what?
Believe me: Sharing interrupts is still a bad problem in this century. At
least when you have to interrupt-heavy devices like firewire and graphics
share
the IRQ.
And its not that re-assuring that the other operating system works: There
you
have a special driver that works around the hardware quirks. And if you
look
at your sound-devices documentation, they will tell you a long list of
probably-not-working controllers and only a small list of working ones.
*A side-note: There is a reason the ffado-README
contains instructions
what
to
report in case of errors. Mostly a verbose log of jack. And the output of
ffado-diag...*
This last bit I dont understand..
What it says, is that ffado (the bit of software you use to make jackd talk
firewire) has an extensive README-file which explains what to do in case
you
need help or want to report a bug. Because most people (you too!) miss to
get
us all the information we devs need. And we feel that our spare-time is
better
spent hacking and fixing then telling people the same things over and over
again. Thats why you really should read the README-files of apps/libraries.
Have fun,
Arnold
PS: Your style of citations is broken and a strange mix of TOFU and
citations...
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5063
days inactive
5064
days old
linux-audio-user@lists.linuxaudio.org
16 comments
7 participants
participants (7)
-
Arnold Krille -
Atte André Jensen -
Jeremy Jongepier -
Julien Claassen -
Niels Mayer -
Paul Davis -
Thomas Hedegaard