From: Benny Sjostrand <gorm@cucumelo.org>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Arthur Peters <amp@singingwizard.org>,
Alsa dev list <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA + jack + xrun = kernel crash
Date: Mon, 19 May 2003 21:16:28 +0200 [thread overview]
Message-ID: <3EC92D8C.3000205@cucumelo.org> (raw)
In-Reply-To: E19HnYU-0003Fd-00@sc8-sf-list1.sourceforge.net
>
>
>aw shoot. of course it returns true: jack tries to link
>capture+playback so that we only have to issue single commands to
>start+stop. damn, i forgot that, sorry.
>
>
>
One thing that would be interesting to known more about is
why does jack not the hangup the machine at once when I start it
without the "-R" flag. (wich will results in a lot more xruns)
Without the "-R" flag: (almost all the times ...)
- jackd runs without locking up the machine
until I try to connect any client.
- after stopping jackd (Ctrl-C) without conecting any client,
the machine dont behave correctly after this, for example
when a 'A' key in the terminal I got any other character, programs
does not start correctly, the machine does not shutdown
correctly, but have not seen any "oops" (but maybe just a random
coincidence ....)
But if it's a spin_lock(...) problem why does not just lock up my
machine in this
case ?
I would interesting to known what happens if someone else could try
starting
the jackd without the "-R" and latest ALSA CVS. (on a SMP machine .. -;)
/Benny
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-19 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 1:54 ALSA + jack + xrun = kernel crash Arthur Peters
2003-05-17 12:27 ` Paul Davis
2003-05-17 12:47 ` Jaroslav Kysela
2003-05-17 20:48 ` Arthur Peters
2003-05-19 16:10 ` Takashi Iwai
2003-05-19 16:38 ` Paul Davis
2003-05-19 19:16 ` Benny Sjostrand [this message]
2003-05-20 8:46 ` Takashi Iwai
2003-05-21 0:32 ` Pieter Palmers
2003-05-21 10:33 ` Takashi Iwai
2003-05-21 11:35 ` Jaroslav Kysela
2003-05-21 11:49 ` Takashi Iwai
2003-05-21 12:54 ` Jaroslav Kysela
[not found] ` <3ECBCF5B.2020807@esat.kuleuven.ac.be>
2003-05-21 23:08 ` Pieter Palmers
2003-05-21 23:50 ` Tarragon Allen
2003-05-22 1:20 ` Paul Davis
2003-05-17 20:57 ` Benny Sjostrand
2003-05-17 21:38 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EC92D8C.3000205@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=amp@singingwizard.org \
--cc=paul@linuxaudiosystems.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.