linux-kernel - Re: [3.4-rc1][Regression][network wireless] 'task xxxx blocked for more than 120 seconds' after resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120405103254.GE2378@redhat.com>
Date:	Thu, 5 Apr 2012 12:32:54 +0200
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Johannes Berg <johannes@...solutions.net>, maciej.rutecki@...il.com
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-wireless@...r.kernel.org,
	netdev <netdev@...r.kernel.org>
Subject: Re: [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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/