From: Ingo Molnar <mingo@elte.hu>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: "Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc6-rt7: Kernel BUG at kernel/rtmutex.c:672
Date: Tue, 28 Nov 2006 21:05:19 +0100 [thread overview]
Message-ID: <20061128200519.GA25364@elte.hu> (raw)
In-Reply-To: <1164737474.15887.10.camel@cmn3.stanford.edu>
* Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
> Nov 28 03:26:39 localhost kernel: Kernel BUG at kernel/rtmutex.c:672
hm, this means the lock was taken twice by the same task: enabling
CONFIG_PROVE_LOCKING ought to tell us the precise locking info and
backtraces that causes this situation. I looked at the code and it wasnt
obvious at first sight. (we should only be holding cache_chain_mutex
here, and l3->list_lock should not be taken at this point.)
Ingo
next prev parent reply other threads:[~2006-11-28 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 18:11 2.6.19-rc6-rt7: Kernel BUG at kernel/rtmutex.c:672 Fernando Lopez-Lezcano
2006-11-28 20:05 ` Ingo Molnar [this message]
2006-11-28 20:06 ` Ingo Molnar
2006-11-28 21:36 ` 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=20061128200519.GA25364@elte.hu \
--to=mingo@elte.hu \
--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 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.