Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
	cc@ccrma.Stanford.EDU
Subject: Re: 2.6.15-rt18, alsa sequencer, rosegarden -> alsa hangs
Date: Tue, 7 Mar 2006 23:06:28 +0100	[thread overview]
Message-ID: <20060307220628.GA27536@elte.hu> (raw)
In-Reply-To: <1141769000.5565.21.camel@cmn3.stanford.edu>


* Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:

> The symptoms are as follows:
>   - start jack using qjackctl
>   - start qsynth (gui front end for fluidsynth, a synth)
>   - start rosegarden (midi sequencer and audio recorder)
>   - load a midi file into rosegarden
>   - midi file plays successfully
>   - close rosegarden
> at this point one of the threads of rosegarden fails to exit and stays
> forever in the process list, in a ps axuw it shows as:
> 
> nando 5484 0.0 0.0 0 0 pts/1    D    13:32   0:00 [rosegardenseque]
> 
> Anything else that I try to stop that touches the alsa sequencer never
> dies (qjackctl, vkeybd, qsynth, etc). Anything I try to start that tries
> to use it does not start. This happened with two widely different

could you get a tasklist-dump? It's either SysRq-T, or:

	echo t > /proc/sysrq-trigger

that should dump all tasks and their backtraces - including the hung 
rosegardensequencer task.

	Ingo

  reply	other threads:[~2006-03-07 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 22:03 2.6.15-rt18, alsa sequencer, rosegarden -> alsa hangs Fernando Lopez-Lezcano
2006-03-07 22:06 ` Ingo Molnar [this message]
2006-03-08  1:29   ` [Alsa-devel] " karsten wiese
2006-03-08  6:53   ` Fernando Lopez-Lezcano
2006-03-08 11:46     ` [Alsa-devel] " Takashi Iwai
2006-03-08 11:48       ` Ingo Molnar
2006-03-08 13:36     ` [Alsa-devel] " karsten wiese
2006-03-08 14:06       ` Ingo Molnar
2006-03-08 17:54         ` [Alsa-devel] " Fernando Lopez-Lezcano

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=20060307220628.GA27536@elte.hu \
    --to=mingo@elte.hu \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=cc@ccrma.Stanford.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox