* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
