23 Feb
2007
23 Feb
'07
12:03 a.m.
Hello list, jackd is shutting down (seemingly randomly) with the
message "zombified - calling shutdown handler".
I am using:
ubuntu feisty latest updates with ubuntustudio packages
Dell Inspiron 630m laptop, 1g ram, pentium m 1.73 ghz
Edirol FA-101 firewire
qjackctl 0.2.21-1
jackd 0.102.20
libfreebob 1.0.0-3
kernel 2.6.20-8-lowlatency
I added the following to limits.conf for pam stuff (I think)
@audio - rtprio 99
@audio - memlock 250000
@audio - nice -10
jack startup command (from qjackctl, I've tried different settings
with sporadic results)
jackd -R -dfreebob -dhw:0 -r44100 -p512 -n2 -i10 -o10
I'm really lost as to what the problem is (I'm no linux guru) and my
settings are only based on copying and pasting from guides around the
net. So if anyone can explain why this is happening or where I've
gone wrong in my setup I would be very grateful.
thanks,
grae
This is the full output from qjackctl:
19:01:46.132 JACK is starting...
19:01:46.133 /usr/bin/jackd -R -dfreebob -dhw:0 -r44100 -p512 -n2 -i10 -o10
19:01:46.148 JACK was started with PID=11204 (0x2bc4).
jackd 0.102.20
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.
loading driver ..
Freebob using Firewire port 0, node -1
19:01:47.282 MIDI connection graph change.
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.
19:01:47.366 MIDI connection change.
19:01:48.173 Server configuration saved to "/home/grae/.jackdrc".
19:01:48.174 Statistics reset.
19:01:48.176 Client activated.
19:01:48.178 Audio connection change.
19:01:48.184 Audio connection graph change.
19:02:17.758 Audio connection graph change.
unknown source port in attempted connection [ZynAddSubFX:out_1]
unknown source port in attempted connection [ZynAddSubFX:out_2]
unknown source port in attempted connection [jamin:out_L]
unknown source port in attempted connection [jamin:out_R]
19:02:17.929 Audio connection change.
19:03:03.193 MIDI connection graph change.
19:03:03.209 MIDI connection graph change.
19:03:03.913 Audio connection graph change.
19:03:03.936 MIDI connection graph change.
19:03:04.017 Audio connection change.
19:03:04.019 MIDI connection change.
19:03:16.170 MIDI connection change.
19:10:58.904 Audio connection graph change.
19:10:59.138 Audio connection graph change.
unknown source port in attempted connection [jamin:out_L]
unknown source port in attempted connection [jamin:out_R]
19:10:59.288 Audio connection change.
19:11:46.100 Audio connection graph change.
19:47:17.784 MIDI connection graph change.
zombified - calling shutdown handler
19:47:17.787 Shutdown notification.
19:47:17.788 Client deactivated.
19:47:17.789 JACK was stopped successfully.
19:47:17.789 Post-shutdown script...
19:47:17.789 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
19:47:18.660 Post-shutdown script terminated with exit status=256.
00:41:50.303 MIDI connection graph change.
00:41:50.310 MIDI connection graph change.
23 Feb
23 Feb
4:02 a.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
Well I'm currently testing this to be sure but I think my issue is
with the "priority" setting of jackd, apparently is has to be above
50?
Currently from the ubuntu repository it defaults to 0 (I
think...maybe I changed it but not sure why I would) and makes me
wonder what use it is having a value like that. Is there any time
that a person would want a priority of zero, or anything less than the
"magical" number of 50? Again, I don't know much about all this stuff
so I'm always trying to piece it together as I go.
Anyway, I've been trying for a long time to get a good linux audio
setup and I think I've finally done it! Thanks to everyone who works
so hard on all this great software. :)
grae
On 2/22/07, grae <drunkenbird(a)gmail.com> wrote:
Hello list, jackd is shutting down (seemingly
randomly) with the
message "zombified - calling shutdown handler".
I am using:
ubuntu feisty latest updates with ubuntustudio packages
Dell Inspiron 630m laptop, 1g ram, pentium m 1.73 ghz
Edirol FA-101 firewire
qjackctl 0.2.21-1
jackd 0.102.20
libfreebob 1.0.0-3
kernel 2.6.20-8-lowlatency
I added the following to limits.conf for pam stuff (I think)
@audio - rtprio 99
@audio - memlock 250000
@audio - nice -10
jack startup command (from qjackctl, I've tried different settings
with sporadic results)
jackd -R -dfreebob -dhw:0 -r44100 -p512 -n2 -i10 -o10
I'm really lost as to what the problem is (I'm no linux guru) and my
settings are only based on copying and pasting from guides around the
net. So if anyone can explain why this is happening or where I've
gone wrong in my setup I would be very grateful.
thanks,
grae
This is the full output from qjackctl:
19:01:46.132 JACK is starting...
19:01:46.133 /usr/bin/jackd -R -dfreebob -dhw:0 -r44100 -p512 -n2 -i10 -o10
19:01:46.148 JACK was started with PID=11204 (0x2bc4).
jackd 0.102.20
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.
loading driver ..
Freebob using Firewire port 0, node -1
19:01:47.282 MIDI connection graph change.
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.
19:01:47.366 MIDI connection change.
19:01:48.173 Server configuration saved to "/home/grae/.jackdrc".
19:01:48.174 Statistics reset.
19:01:48.176 Client activated.
19:01:48.178 Audio connection change.
19:01:48.184 Audio connection graph change.
19:02:17.758 Audio connection graph change.
unknown source port in attempted connection [ZynAddSubFX:out_1]
unknown source port in attempted connection [ZynAddSubFX:out_2]
unknown source port in attempted connection [jamin:out_L]
unknown source port in attempted connection [jamin:out_R]
19:02:17.929 Audio connection change.
19:03:03.193 MIDI connection graph change.
19:03:03.209 MIDI connection graph change.
19:03:03.913 Audio connection graph change.
19:03:03.936 MIDI connection graph change.
19:03:04.017 Audio connection change.
19:03:04.019 MIDI connection change.
19:03:16.170 MIDI connection change.
19:10:58.904 Audio connection graph change.
19:10:59.138 Audio connection graph change.
unknown source port in attempted connection [jamin:out_L]
unknown source port in attempted connection [jamin:out_R]
19:10:59.288 Audio connection change.
19:11:46.100 Audio connection graph change.
19:47:17.784 MIDI connection graph change.
zombified - calling shutdown handler
19:47:17.787 Shutdown notification.
19:47:17.788 Client deactivated.
19:47:17.789 JACK was stopped successfully.
19:47:17.789 Post-shutdown script...
19:47:17.789 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
19:47:18.660 Post-shutdown script terminated with exit status=256.
00:41:50.303 MIDI connection graph change.
00:41:50.310 MIDI connection graph change.
10:56 a.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
grae wrote:
Well I'm currently testing this to be sure but I
think my issue is
with the "priority" setting of jackd, apparently is has to be above
50?
Currently from the ubuntu repository it defaults to 0 (I
think...maybe I changed it but not sure why I would) and makes me
wonder what use it is having a value like that. Is there any time
that a person would want a priority of zero, or anything less than the
"magical" number of 50? Again, I don't know much about all this stuff
so I'm always trying to piece it together as I go.
The magic in this number is
that this is the default value assigned to
threaded IRQ handlers (at least on my system by rtirq). This means that
when you run jackd with a priority higher than 50, it won't be
interrupted by hardware interrupts from e.g. vga devices or harddisks.
Note that it is best to make sure that the IRQ handler of your ohci1394
card is higher than the priority you run jack with (I make it 90).
see:
http://freebob.sourceforge.net/index.php/IRQ_Threading_and_Priorities
Another tip: due to libfreebob internals, it is better to use 3 smaller
periods instead of 2 larger, e.g. -n3 -p256 will probably work better
than -n2 -p512.
Anyway, I've been trying for a long time to get a good linux audio
setup and I think I've finally done it! Thanks to everyone who works
so hard on all this great software. :)
you're welcome ;)
Pieter Palmers
FreeBoB developer
24 Feb
24 Feb
6:14 p.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
2007/2/23, Pieter Palmers <pieterp(a)joow.be>be>:
Another tip: due to libfreebob internals, it is better
to use 3 smaller
periods instead of 2 larger, e.g. -n3 -p256 will probably work better
than -n2 -p512.
Hmm, using 2x128 and 2x256 proved to be more stable than 3x256 at my setup...
Arnold
--
visit http://www.arnoldarts.de/
---
Wenn man mit Raubkopien Bands wie Brosis oder Britney Spears wirklich
verhindern könnte, würde ich mir noch heute einen Stapel Brenner und
einen Sack Rohlinge kaufen.
7:53 p.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
On 2/24/07, Arnold Krille <arnold.krille(a)gmail.com> wrote:
2007/2/23, Pieter Palmers <pieterp(a)joow.be>be>:
Thanks for your help,
Ok well I seem to still get the zombies. I got the rtirq script and I
*think* it's working. I configured it just like the freebob site says
output from "rtirq status":
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
779 FF 80 - 120 0.0 S< IRQ-8
2076 FF 75 - 115 0.0 S< IRQ-16
2118 FF 64 - 104 0.0 S< IRQ-17
2166 FF 63 - 103 0.0 S< IRQ-18
2172 FF 62 - 102 0.0 S< IRQ-19
815 FF 60 - 100 0.0 S< IRQ-1
814 FF 59 - 99 0.2 S< IRQ-12
4 FF 50 - 90 0.0 S softirq-high/0
5 FF 50 - 90 0.0 S softirq-timer/0
6 FF 50 - 90 0.0 S softirq-net-tx/
7 FF 50 - 90 0.0 S softirq-net-rx/
8 FF 50 - 90 0.0 S softirq-block/0
9 FF 50 - 90 0.0 S softirq-tasklet
10 FF 50 - 90 0.0 S softirq-sched/0
11 FF 50 - 90 0.0 S softirq-hrtimer
12 FF 50 - 90 0.0 S softirq-rcu/0
42 FF 50 - 90 0.0 S< IRQ-9
2215 FF 50 - 90 0.0 S< IRQ-14
2216 FF 50 - 90 0.0 S< IRQ-15
I used "/proc/interrupts" to show the irqs, specifically noted IRQ 16
16: 741 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5, ohci1394, HDA
Intel, i915@pci:0000:00:02.0
It seems that my firewire device is sharing an IRQ with a couple usb
ports, the internal soundcard and internal video. My guess is that
this isn't good. Should I attempt the give the firewire it's own IRQ
and if so, could you point me in the direction of how to do that? I'm
figuring this stuff out as I go here so it's hard to know how to
proceed sometimes.
Also, when setting the jack priority do I want it to be just under the
firewire device? for example: if IRQ 16 was just the firewire
(running at 75), then running jack at 74 would make sense?
grae
Another tip: due to libfreebob internals, it is
better to use 3 smaller
periods instead of 2 larger, e.g. -n3 -p256 will probably work better
than -n2 -p512.
Hmm, using 2x128 and 2x256 proved to be more stable than 3x256 at my setup...
Arnold
--
visit http://www.arnoldarts.de/
---
Wenn man mit Raubkopien Bands wie Brosis oder Britney Spears wirklich
verhindern könnte, würde ich mir noch heute einen Stapel Brenner und
einen Sack Rohlinge kaufen.
25 Feb
25 Feb
4:34 a.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
grae wrote:
On 2/24/07, Arnold Krille
<arnold.krille(a)gmail.com> wrote:
> 2007/2/23, Pieter Palmers <pieterp(a)joow.be>be>:
> > Another tip: due to libfreebob internals, it is better to use 3 smaller
> > periods instead of 2 larger, e.g. -n3 -p256 will probably work better
> > than -n2 -p512.
>
> Hmm, using 2x128 and 2x256 proved to be more stable than 3x256 at my
> setup...
'theoretically' that is very strange, I think there is a problem elsewhere.
Ok well I seem to still get the zombies. I got the
rtirq script and I
*think* it's working. I configured it just like the freebob site says
output from "rtirq status":
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
779 FF 80 - 120 0.0 S< IRQ-8
2076 FF 75 - 115 0.0 S< IRQ-16
2118 FF 64 - 104 0.0 S< IRQ-17
2166 FF 63 - 103 0.0 S< IRQ-18
2172 FF 62 - 102 0.0 S< IRQ-19
815 FF 60 - 100 0.0 S< IRQ-1
814 FF 59 - 99 0.2 S< IRQ-12
4 FF 50 - 90 0.0 S softirq-high/0
5 FF 50 - 90 0.0 S softirq-timer/0
6 FF 50 - 90 0.0 S softirq-net-tx/
7 FF 50 - 90 0.0 S softirq-net-rx/
8 FF 50 - 90 0.0 S softirq-block/0
9 FF 50 - 90 0.0 S softirq-tasklet
10 FF 50 - 90 0.0 S softirq-sched/0
11 FF 50 - 90 0.0 S softirq-hrtimer
12 FF 50 - 90 0.0 S softirq-rcu/0
42 FF 50 - 90 0.0 S< IRQ-9
2215 FF 50 - 90 0.0 S< IRQ-14
2216 FF 50 - 90 0.0 S< IRQ-15
I used "/proc/interrupts" to show the irqs, specifically noted IRQ 16
16: 741 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5,
ohci1394, HDA
Intel, i915@pci:0000:00:02.0
Can you provide the complete /proc/interrupts?
It seems that my firewire device is sharing an IRQ with a couple usb
ports, the internal soundcard and internal video. My guess is that
this isn't good. Should I attempt the give the firewire it's own IRQ
and if so, could you point me in the direction of how to do that? I'm
figuring this stuff out as I go here so it's hard to know how to
proceed sometimes.
This is a common problem with laptops and i have been struggling
with
this myself, and AFAIK the only thing you can hope is that your system
has an IO-APIC, and that it is routed in a favorable fashion (hardware
that is). Try and enable the IO-APIC in the kernel and see if it comes
up (some lines having the word IO-APIC should appear in /proc/interrupts.)
Note that intel mac mini's seem to have the same problem, but worse:
almost everything shares one interrupt. Imagine: video + SATA controller
+ audio card.
But as I said, this is all AFAIK, I really hope that someone stands up
and explains how to fully split these interrupts...
Also, when setting the jack priority do I want it to be just under the
firewire device? for example: if IRQ 16 was just the firewire
(running at 75), then running jack at 74 would make sense?
You should take into
account that libfreebob will also create threads to
perform the packet handling, and those are running at jack_prio+10. It
is therefore best to run jackd with a priority of less than ohci_prio - 10.
27 Feb
27 Feb
10:52 p.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
ok thanks Pieter. It lists IO-APIC-fasteoi for the IRQ in question.
I'll look into it some more and see where I get.
Thanks for your help. :)
grae
On 2/25/07, Pieter Palmers <pieterp(a)joow.be> wrote:
grae wrote:
On 2/24/07, Arnold Krille
<arnold.krille(a)gmail.com> wrote:
> 2007/2/23, Pieter Palmers <pieterp(a)joow.be>be>:
> > Another tip: due to libfreebob internals, it is better to use 3 smaller
> > periods instead of 2 larger, e.g. -n3 -p256 will probably work better
> > than -n2 -p512.
>
> Hmm, using 2x128 and 2x256 proved to be more stable than 3x256 at my
> setup...
'theoretically' that is very strange, I think there is a problem elsewhere.
Ok well I seem to still get the zombies. I got
the rtirq script and I
*think* it's working. I configured it just like the freebob site says
output from "rtirq status":
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
779 FF 80 - 120 0.0 S< IRQ-8
2076 FF 75 - 115 0.0 S< IRQ-16
2118 FF 64 - 104 0.0 S< IRQ-17
2166 FF 63 - 103 0.0 S< IRQ-18
2172 FF 62 - 102 0.0 S< IRQ-19
815 FF 60 - 100 0.0 S< IRQ-1
814 FF 59 - 99 0.2 S< IRQ-12
4 FF 50 - 90 0.0 S softirq-high/0
5 FF 50 - 90 0.0 S softirq-timer/0
6 FF 50 - 90 0.0 S softirq-net-tx/
7 FF 50 - 90 0.0 S softirq-net-rx/
8 FF 50 - 90 0.0 S softirq-block/0
9 FF 50 - 90 0.0 S softirq-tasklet
10 FF 50 - 90 0.0 S softirq-sched/0
11 FF 50 - 90 0.0 S softirq-hrtimer
12 FF 50 - 90 0.0 S softirq-rcu/0
42 FF 50 - 90 0.0 S< IRQ-9
2215 FF 50 - 90 0.0 S< IRQ-14
2216 FF 50 - 90 0.0 S< IRQ-15
I used "/proc/interrupts" to show the irqs, specifically noted IRQ 16
16: 741 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5,
ohci1394, HDA
Intel, i915@pci:0000:00:02.0
Can you provide the complete /proc/interrupts?
It seems that my firewire device is sharing an IRQ with a couple usb
ports, the internal soundcard and internal video. My guess is that
this isn't good. Should I attempt the give the firewire it's own IRQ
and if so, could you point me in the direction of how to do that? I'm
figuring this stuff out as I go here so it's hard to know how to
proceed sometimes.
This is a common problem with laptops and i have been
struggling with
this myself, and AFAIK the only thing you can hope is that your system
has an IO-APIC, and that it is routed in a favorable fashion (hardware
that is). Try and enable the IO-APIC in the kernel and see if it comes
up (some lines having the word IO-APIC should appear in /proc/interrupts.)
Note that intel mac mini's seem to have the same problem, but worse:
almost everything shares one interrupt. Imagine: video + SATA controller
+ audio card.
But as I said, this is all AFAIK, I really hope that someone stands up
and explains how to fully split these interrupts...
Also, when setting the jack priority do I want it to be just under the
firewire device? for example: if IRQ 16 was just the firewire
(running at 75), then running jack at 74 would make sense?
You should take into
account that libfreebob will also create threads to
perform the packet handling, and those are running at jack_prio+10. It
is therefore best to run jackd with a priority of less than ohci_prio - 10.
28 Feb
28 Feb
10:30 a.m.
New subject: [linux-audio-user] Re: jackd "zombified - calling shutdown handler"
On 2/25/07, Pieter Palmers <pieterp(a)joow.be> wrote:
But as I said, this is all AFAIK, I really hope that
someone stands up
and explains how to fully split these interrupts...
Usually you can't - the interrupt routing is hard wired and vendors
like to put everything on the same line because it's cheaper.
Lee
6554
days inactive
6560
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Arnold Krille -
grae -
Lee Revell -
Pieter Palmers