From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-wireless@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [3.4-rc1][Regression][network wireless] 'task xxxx blocked for more than 120 seconds' after resume
Date: Thu, 5 Apr 2012 20:37:37 +0200 [thread overview]
Message-ID: <201204052037.37497.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20120405103254.GE2378@redhat.com>
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
next prev parent reply other threads:[~2012-04-05 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201204022157.05598.maciej.rutecki@gmail.com>
2012-04-03 8:07 ` [3.4-rc1][Regression][network wireless] 'task xxxx blocked for more than 120 seconds' after resume Johannes Berg
2012-04-05 10:32 ` Stanislaw Gruszka
2012-04-05 18:37 ` Maciej Rutecki [this message]
[not found] ` <201204052037.37497.maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-05 18:56 ` Johannes Berg
2012-04-05 20:08 ` Maciej Rutecki
2012-04-05 20:23 ` Johannes Berg
2012-04-05 21:01 ` Francois Romieu
2012-04-11 19:37 ` Maciej Rutecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201204052037.37497.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sgruszka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).