* David Miller <davem@davemloft.net> wrote:

quoted text
> > WARNING: at kernel/lockdep_proc.c:267 lockdep_stats_show()
> > Call Trace:
> >  [0000000000492704] lockdep_stats_show+0x6ac/0x6c0
> >  [00000000004eb4b4] seq_read+0x5c/0x340
> >  [000000000050b2bc] proc_reg_read+0x64/0xa0
> >  [00000000004cd72c] vfs_read+0x74/0x120
> >  [00000000004cdb4c] sys_read+0x34/0x60
> >  [00000000004062d4] linux_sparc_syscall32+0x3c/0x40
> >  [0000000000012ff4] 0x12ffc
> 
> Please turn off lockdep on sparc64, currently it not reliable.  I have 
> many things to audit, including how the stack frames are presented to 
> the lockdep layer.
> 
> So any problem you run into can be due to issues like that.

is this anything the core lockdep code could help improve? Let us know 
if any aspect is hindering you.

	Ingo
--
unsubscribe notice
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/