On czwartek, 5 kwietnia 2012 o 20:56:23 Johannes Berg wrote: > On Thu, 2012-04-05 at 20:37 +0200, Maciej Rutecki wrote: > > On czwartek, 5 kwietnia 2012 o 12:32:54 Stanislaw Gruszka wrote: > > > On Tue, Apr 03, 2012 at 10:07:49AM +0200, Johannes Berg wrote: > > > > -ilw > > > > +netdev > > > > > > > > I have no idea what this could be, but I'm almost certain it's not > > > > caused by our wireless driver. Looks more like rtl8169 is to blame. > > > > > > I'm not sure. Looks like there is deadlock or infinite loop in process > > > that holds rtnl lock. This can be wireless driver, wired driver or > > > generic network code bug. > > > > > > Maciej, please recompile with CONFIG_LOCKDEP and check if it will not > > > find any deadlock. If not, when problem will happen please do > > > > Did you mean "CONFIG_LOCKDEP_SUPPORT"? > > No, _SUPPORT means you could enable CONFIG_LOCKDEP, but we would like to > see this with CONFIG_LOCKDEP enabled. > > johannes Dmesg when CONFIG_LOCKDEP is set: http://mrutecki.pl/download/kernel/3.4-rc1/netdev_resume/dmesg-lockdep.txt Regards -- Maciej Rutecki http://www.mrutecki.pl -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
