30 Dec
2008
30 Dec
'08
3:34 p.m.
I'm running Debian Lenny on a custom 2.6.26.8-rt12 kernel. I notice
once jackd starts, it cannot be killed. kill -9 leaves the jackd
process in state DLs
D Uninterruptible sleep (usually IO)
L has pages locked into memory (for real-time and custom IO)
s is a session leader
Running jackd -R -P70 -dalsa -dhw:0 -r44100 -p128 -n2 -Xseq
I get same behaviour from kernel 2.6.26.6-rt11.
Running in non-RT mode shows same behaviour
ice-1712 chipset M-Audio Delta 44
jackd version 0.109.2 tmpdir /dev/shm protocol 22
I built jack 0.116.x, alsa 1.0.18x, and still get same behaviour.
This kernels alsa driver is 0.16, upgraded to current 1.0.18a, same behaviour.
This whole situation is disheartening as I once had a working setup on
an older Ubuntu distribution where I could use skype with alsa's jack
plugin (yes, I know, Ubuntu doesn't ship it, I had to rebuild
libasound2-plugins pkg), but other alsa/jack issues forced me to have
to dump Ubuntu altogether.
I discovered the inability to kill jackd process while trying to
troubleshoot skypes use of alsa's jack plugin crashing jackd. Also
discovered any process that invoked that plugin would crash jackd when
the plugin thread disconnected from jackd. In all it seems my jack
setup is now unstable.
Any help in troubleshooting these problems would be appreciated, thank you.
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
30 Dec
30 Dec
4:42 p.m.
"R Dicaire" <kritek(a)gmail.com> writes:
I'm running Debian Lenny on a custom 2.6.26.8-rt12
kernel. I notice
once jackd starts, it cannot be killed. kill -9 leaves the jackd
process in state DLs
Running jackd -R -P70 -dalsa -dhw:0 -r44100 -p128 -n2 -Xseq
I get same behaviour from kernel 2.6.26.6-rt11.
This looks like the 2.6.26 MIDI sequencer problem -- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
I've gone back to 2.6.24 for now, but as I recall, if you don't care
about MIDI, you can start jackd with -Xraw (or with no -X option) and
it'll still do audio happily.
It'd be really nice to have a fix for this, since 2.6.24 occasionally
locks up for me when I've got realtime stuff running (whereas 2.6.26 is
admirably well-behaved aside from the complete lack of MIDI). Does
anyone know whether MIDI's working again in the new RT tree?
--
Adam Sampson <ats(a)offog.org> <http://offog.org/>
5:20 p.m.
On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson <ats(a)offog.org> wrote:
This looks like the 2.6.26 MIDI sequencer problem --
MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
31 Dec
31 Dec
1:44 a.m.
On Tue, Dec 30, 2008 at 04:20:11PM -0500, R Dicaire wrote:
On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
MIDI doesn't work in 2.6.26???!
Is that for real? Is it really a kernel problem or an ALSA problem? Is there a
workaround?
I thought the ALSA drivers were or could be obtained and compiled separately from the
kernel though.
-ken
This looks like the 2.6.26 MIDI sequencer problem
-- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
1:52 a.m.
On Wed, Dec 31, 2008 at 12:44 AM, Ken Restivo <ken(a)restivo.org> wrote:
I thought the ALSA drivers were or could be obtained
and compiled separately from the kernel though.
Alsa drivers have to be built against the kernel src tree of the
current running kernel, according to the INSTALL in the alsa-drivers
src tree.
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
4:49 a.m.
On Tue, 2008-12-30 at 21:44 -0800, Ken Restivo wrote:
On Tue, Dec 30, 2008 at 04:20:11PM -0500, R Dicaire
wrote:
The problem I see is with the rt patch applied. And only when
interfacing with external hardware midi interfaces. A partial workaround
made midi input work, but the internal timer has problems.
I have not checked midi under 2.6.26-rt12 yet...
-- Fernando
On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
MIDI doesn't work in 2.6.26???!
Is that for real? Is it really a kernel problem or an ALSA problem?
Is there a workaround? This looks like the 2.6.26 MIDI sequencer problem
-- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
11:14 p.m.
On Wed, Dec 31, 2008 at 12:49:26AM -0800, Fernando Lopez-Lezcano wrote:
On Tue, 2008-12-30 at 21:44 -0800, Ken Restivo wrote:
I have a 2.6.26.8-rt12 sitting here built, ready to try booting off of it.
What exactly is the MIDI problem, and how could I duplicate it here? I'd be happy to
test with this kernel (on a x86 Atom) and see if it is solved.
-ken
On Tue, Dec 30, 2008 at 04:20:11PM -0500, R
Dicaire wrote:
The problem I see is with the rt patch applied. And only when
interfacing with external hardware midi interfaces. A partial workaround
made midi input work, but the internal timer has problems.
I have not checked midi under 2.6.26-rt12 yet... On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
MIDI doesn't work in 2.6.26???!
Is that for real? Is it really a kernel problem or an ALSA problem?
Is there a workaround? This looks like the 2.6.26 MIDI sequencer problem
-- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ? 
1 Jan
1 Jan
12:40 a.m.
I have a 2.6.26.8-rt12 sitting here built, ready to
try booting off of it.
What exactly is the MIDI problem, and how could I duplicate it here? I'd be happy to
test with this kernel (on a x86 Atom) and see if it is solved.
I have the same problem ...with the rt patches applied I can't kill any app that use
the alsa-seq,
or jack maybe because I use the -X
I dont remember exacly but I thing the last kernel with rt patches that works for me was
2.6.24.3, maybe .4 works too.
-
Josep Andreu <holborn(a)telefonica.net>
12:54 a.m.
On Wed, Dec 31, 2008 at 11:41 PM, Josep Andreu <holborn(a)telefonica.net> wrote:
> I have a 2.6.26.8-rt12 sitting here built, ready to try booting off of it.
>
> What exactly is the MIDI problem, and how could I duplicate it here? I'd be happy
to test with this kernel (on a x86 Atom) and see if it is solved.
btw, I'm already using this kernel. I can't use my MidiMan Uno usb
iface either :(
can't seem to use jack-rack either as it tries to open alsa seq...what a mess :(
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
7:23 p.m.
On Wed, 2008-12-31 at 19:13 -0800, Ken Restivo wrote:
On Wed, Dec 31, 2008 at 12:49:26AM -0800, Fernando
Lopez-Lezcano wrote:
The problem I see only happens when you use the ALSA sequencer API with
any external MIDI interface. The sequencer API works fine as long as
external ports are not involved. And if you use an external MIDI
interface through the rawmidi interface it works fine. The combination
of rawmidi + sequencer fails...
-- Fernando
On Tue, 2008-12-30 at 21:44 -0800, Ken Restivo
wrote:
I have a 2.6.26.8-rt12 sitting here built, ready to try booting off of it.
What exactly is the MIDI problem, and how could I duplicate it here? I'd
be happy to test with this kernel (on a x86 Atom) and see if it is solved. On Tue, Dec 30, 2008 at 04:20:11PM -0500, R
Dicaire wrote:
The problem I see is with the rt patch applied. And only when
interfacing with external hardware midi interfaces. A partial workaround
made midi input work, but the internal timer has problems.
I have not checked midi under 2.6.26-rt12 yet... On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
> This looks like the 2.6.26 MIDI sequencer problem -- MIDI doesn't work,
> and after jackd has opened the sequencer device for the first time,
> it'll hang trying to close it. Future attempts to open the sequencer
> device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
MIDI doesn't work in 2.6.26???!
Is that for real? Is it really a kernel problem or an ALSA problem?
Is there a workaround?
7:32 p.m.
On Thu, Jan 1, 2009 at 6:22 PM, Fernando Lopez-Lezcano
<nando(a)ccrma.stanford.edu> wrote:
The problem I see only happens when you use the ALSA
sequencer API with
any external MIDI interface. The sequencer API works fine as long as
external ports are not involved. And if you use an external MIDI
interface through the rawmidi interface it works fine. The combination
of rawmidi + sequencer fails...
While I can start jackd with -Xraw or -Xseq, both of these options
prevent killing the jackd process.
jack-rack, on startup, tries to open the seq device, and just hangs, I
can kill it, but jack-rack won't run since it cannot finish its
initialization.
qtpod, a Line6 Pod editor that uses external midi interface, cannot
init the interface, and fails to communicate
with the Pod device.
I had to remove all midi references from ardours config in order to
get it to start, and run.
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
31 Dec
31 Dec
7:27 a.m.
On Tue, Dec 30, 2008 at 09:44:27PM -0800, Ken Restivo wrote:
MIDI doesn't work in 2.6.26???!
Well, for me and several other people on this list, certainly...
I thought the ALSA drivers were or could be obtained
and compiled
separately from the kernel though.
Yup, I tried that -- I built alsa-driver 1.0.18a against 2.6.26.6-rt11,
and the problem's still there, so I guess it's something more
fundamental.
--
Adam Sampson <ats(a)offog.org> <http://offog.org/>
5:26 a.m.
R Dicaire wrote:
On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
Is this a way of allowing alsa apps to talk to jack? If so I would like
to have a go at setting it up but don't know where to start. Do I need
to compile my own libasound2, or the alsa kernel modules? (I've checked
and /usr/lib/alsa-lib doesn't include this plugin.) I'm running linux
mint, which is based on Ubuntu. I've googled for a definitive guide but
can't find one.
andy
This looks like the 2.6.26 MIDI sequencer problem
-- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
11:05 a.m.
R Dicaire wrote:
On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson
<ats(a)offog.org> wrote:
hallo,
i am not sure if it has anything to do with your issue, but as you say,
it happens only when you start jackd with -Xseq, it could be that this
is the root of the problem. i discovered a trouble in ardour, when
running jackd with -Xseq explicitly. you may have a look here:
http://tracker.ardour.org/view.php?id=2497
in this case, the issue for me is reproducible very easy, but only if
running with -Xseq.
ardour2.7.1, jackd0.116.1, alsa1.0.17, Linux 2.6.25.4-rt5 #2 PREEMPT RT
know that this does not save your problem, but perhaps it is interesting.
cheers,
doc
This looks like the 2.6.26 MIDI sequencer problem
-- MIDI doesn't work,
and after jackd has opened the sequencer device for the first time,
it'll hang trying to close it. Future attempts to open the sequencer
device then fail because it's in use.
Ahhhhhhhh, I was never aware there was a midi issue...jackd could be
killed when I didn't use -X, excellent.
Thank you VERY much.
Now here's another situation. I've built alsa
and jack. I installed
them into custom locations. In my users .asoundrc
I have a pcm device that calls the jack plugin. How would I get calls
to this plugin to use my custom built
/usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of
the system one in /usr/lib/alsa-lib ?
30 Dec
30 Dec
4:45 p.m.
Hi!
I roughly have the same setup. Lenny, self-bult kernel (rt-patched and
non-rt-patched), Jack 0.112.0.
Did you ever try skipping the -P70? I don't do it and it works nicely. No
xrun no nothing on the vanilla 2.6.23, still very OK, with lots of delays and
some xruns on the rt-patched kernel (2.6.24-2.6.26). Even my card is almost
the same. My alsa is built-in though and I don't use the alsa-jack plugin
rarely. But still no trouble with that.
/dev/shm is not a very good idea though. Had my strange problems with that.
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
5:27 p.m.
On Tue, Dec 30, 2008 at 3:45 PM, Julien Claassen <julien(a)c-lab.de> wrote:
almost the same. My alsa is built-in though and I
don't use the alsa-jack
plugin rarely. But still no trouble with that.
If you could, create a custom pcm device in .asoundrc using the jack
plugin, and try skype using that pcm device.
pcm.skype {
type plug
slave {
pcm "configvoip"
}
}
pcm.configvoip {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_1
}
}
This worked fine under Lenny until a major alsa update came down the
pipe when jack port names were changed from alsa_pcm: to system:
sometime ago.
I'd like to know if you experience the same issue I have, the plugin
crashing jackd.
Thanks
--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u
5:40 p.m.
Hi!
Sorry, I can't test it with skype. I'm blind. But I tested it with yatm (yet
another time machine) and some other piece of software. I think I accidentally
ran fluidsynth with that. And it worked. Wait I'm trying yatm...
Perfect! Speeding up/slowing, pitching... Not even a delay or xrun. JACK
still 100% fine.
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
5834
days inactive
5836
days old
linux-audio-user@lists.linuxaudio.org
16 comments
8 participants
participants (8)
-
Adam Sampson -
andy baxter -
Dragan Noveski -
Fernando Lopez-Lezcano -
Josep Andreu -
Julien Claassen -
Ken Restivo -
R Dicaire