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"? $ cat /boot/config-3.4.0-rc1 | grep CONFIG_LOCKDEP CONFIG_LOCKDEP_SUPPORT=y > > echo w > /proc/sysrq-trigger > dmesg -c > dmesg1.txt http://mrutecki.pl/download/kernel/3.4-rc1/netdev_resume/dmesg1.txt > echo t > /proc/sysrq-trigger > dmesg > dmesg2.txt http://mrutecki.pl/download/kernel/3.4-rc1/netdev_resume/dmesg2.txt > > and provide those files. > > Additionally there are also lot in dmesg: > > netlink: 140 bytes leftover after parsing attributes. > > This need to be investigated as well. Perhaps you could modify error > message, to show what netlink messages/attributes are processed. > > Thanks > Stanislaw BTW. From tomorrow till Tuesday I'll be on vacation, so until then I could respond to the e-mails. 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
