On Fri, Mar 07, 2008 at 12:19:03PM +0200, Denys Fedoryshchenko wrote:
quoted text
> Ok, i will proceed and will try all required options after few hours (need to 
> go another city, work).
> I will try to set max as possible debug options.

Max could be too much, but e.g. this is sometimes helpful too:
CONFIG_DEBUG_LIST is not set

BTW, you didn't write yet if with min/no debugging, no 4KSTACKS and
lockdep off there is any change in these lockups?

And no need to hurry...

quoted text
> On bug_feb.txt it is triggering ONLY lockdep warning, but full network lockup 
> occur very rarely. But even it happens with me 2 times, i am not sure it is 
> same problem. Let's stick maybe to this one (lockdep warning) which is easy 
> to reproduce.
> I will open also bugzilla report.

Send Re: here with a bugzilla number.

quoted text
> 
> Regarding testing with compiled in modules, i did
> CONFIG_IFB=y 
> CONFIG_DUMMY=y
> CONFIG_BONDING=y
> CONFIG_MACVLAN=y 
> CONFIG_EQUALIZER=y
> CONFIG_TUN=y
> 
> It is still triggering lockdep.
> Here is full dmesg:
> http://www.nuclearcat.com/files/dmesg_1234.txt

OK, but it seems still without my last patch to ifb?

Thanks,
Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html