From: Ingo Molnar <mingo@elte.hu>
To: Takashi Iwai <tiwai@suse.de>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
cc@ccrma.Stanford.EDU
Subject: Re: Re: 2.6.15-rt18, alsa sequencer, rosegarden -> alsa hangs
Date: Wed, 8 Mar 2006 12:48:47 +0100 [thread overview]
Message-ID: <20060308114847.GA20591@elte.hu> (raw)
In-Reply-To: <s5h4q29rwfg.wl%tiwai@suse.de>
* Takashi Iwai <tiwai@suse.de> wrote:
> > > 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.
> >
> > I'll try to do that tomorrow.
>
> That'll be helpful. A deadlocked mutex could be easily found by a
> backtrace.
furthermore, in the -rt kernel (if PREEMPT_RT and DEBUG_DEADLOCKS is
enabled), all locks will also be printed, and their owners, and the site
where they got acquired, etc. A deadlocked mutex/semaphore should in
fact be detected by the kernel, if those options are enabled.
Ingo
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-08 11:48 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
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 [this message]
2006-03-08 13:36 ` 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=20060308114847.GA20591@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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox