lkml.org 
[lkml]   [2006]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.17-rc5-mm1
Ingo Molnar wrote:
> * Andrew Morton <akpm@osdl.org> wrote:
>
>
>>>EIP is at check_deadlock+0x15/0xe0
>
>
>>> <c012b77b> check_deadlock+0xa5/0xe0 <c012b922>
>>>debug_mutex_add_waiter+0x46/0x55
>>> <c02d50de> __mutex_lock_slowpath+0x9e/0x1c0 <c0160061>
>>>lookup_create+0x19/0x5b
>>> <c016043a> sys_mkdirat+0x4c/0xc3 <c01604c0> sys_mkdir+0xf/0x13
>>> <c02d6217> syscall_call+0x7/0xb
>>
>>Looks like the lock validator came unstuck. But there's so much other
>>crap happening in there it's hard to tell. Did you try it without all
>>the lockdep stuff enabled?
>
>
> 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

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

M.


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

\
 
 \ /
  Last update: 2006-05-31 23:30    [W:1.154 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site