Re: 2.6.17-rc5-mm1

From: Martin J. Bligh
Date: Wed May 31 2006 - 17:42:19 EST


Ingo Molnar wrote:
* Martin J. Bligh <mbligh@xxxxxxxxxx> wrote:


AFAICS this isnt the lock validator but the normal mutex debugging code (CONFIG_DEBUG_MUTEXES). The log does not indicate that lockdep was enabled.

Buggered if I know how that got turned on. I thought we turned it off by default now? That's what screwed up all the perf results before.

http://test.kernel.org/abat/33803/build/dotconfig
That's the build config it ran with.

CONFIG_DEBUG_MUTEXES=y


still ... it shouldnt have crashed on us. I did change it in -mm1 so i'll take a look tomorrow.


Grrr. Humpf. I can't see the option being turned on for lockdep ...
what was the config option, and is it enabled by default?

In the -mm1 patch:

config DEBUG_MUTEXES
- bool "Mutex debugging, deadlock detection"
- default n
+ bool "Mutex debugging, basic checks"
+ default y

Please don't do thatas a default.
It fucks up all the performance checking ;-(


M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/