From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Arthur Peters <amp@singingwizard.org>,
Alsa dev list <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA + jack + xrun = kernel crash
Date: Tue, 20 May 2003 10:46:56 +0200 [thread overview]
Message-ID: <s5hsmrac8e7.wl@alsa2.suse.de> (raw)
In-Reply-To: <E19HnYU-0003Fd-00@sc8-sf-list1.sourceforge.net>
At Mon, 19 May 2003 12:38:14 -0400,
Paul Davis wrote:
>
> >could you check whether snd_pcm_stream_linked() returns really only
> >zero? if yes, the code path shouldn't include the complicated locks
>
> 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.
ok, i found a serious typo in pcm_native.c, which i guess as the
culprit.
could you try the cvs version?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
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-20 8:46 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
2003-05-20 8:46 ` Takashi Iwai [this message]
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=s5hsmrac8e7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=amp@singingwizard.org \
--cc=paul@linuxaudiosystems.com \
/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.