lkml.org 
[lkml]   [2012]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [3.4-rc1][Regression][network wireless] 'task xxxx blocked for more than 120 seconds' after resume
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

echo w > /proc/sysrq-trigger
dmesg -c > dmesg1.txt
echo t > /proc/sysrq-trigger
dmesg > 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



\
 
 \ /
  Last update: 2012-04-05 12:37    [W:0.156 / U:0.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site