On Sat, Feb 16, 2008 at 12:25:31PM +0200, Denys Fedoryshchenko wrote: > Thanks, i will try it. > You think lockdep can be buggy?
Just like every code... But the main reason is it has quite meaningful overhead, so could be right "in production" only after lockups happen. But if it doesn't report anything anyway... Your report shows there are quite long paths of calls during softirqs with some actions (ipt + mirred here?) and qdiscs, so if I'm not wrong with this stack problem, this would need some optimization. And, of course, there could be some additional bugs involved around too: otherwise it seems this should happen more often. But I don't expect you would try to debug this on your servers, so I hope, it simply will be found BTW some day... Regards, Jarek P. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
