From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Stanislaw Gruszka <sgruszka@redhat.com>,
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: Wed, 11 Apr 2012 21:37:47 +0200 [thread overview]
Message-ID: <201204112137.47854.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20120405210122.GA12135@electric-eye.fr.zoreil.com>
On czwartek, 5 kwietnia 2012 o 23:01:22 Francois Romieu wrote:
> Johannes Berg <johannes@sipsolutions.net> :
> > On Thu, 2012-04-05 at 22:08 +0200, Maciej Rutecki wrote:
> > > Dmesg when CONFIG_LOCKDEP is set:
> > >
> > > http://mrutecki.pl/download/kernel/3.4-rc1/netdev_resume/dmesg-lockdep.
> > > txt
> >
> > Looks like rtl8169's fault:
> Fix is on the way to mainline, see http://patchwork.ozlabs.org/patch/150541
Seems be resolved in -rc2. Only in dmesg still I have messages "netlink: 140
bytes leftover after parsing attributes.". It seems be another issue.
Thanks
--
Maciej Rutecki
http://www.mrutecki.pl
prev parent reply other threads:[~2012-04-11 19: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
[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 [this message]
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=201204112137.47854.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=romieu@fr.zoreil.com \
--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).