From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath9k@venema.h4ckr.net, Herbert Xu <herbert@gondor.hengli.com.au>
Subject: Re: Lockup inside of stop_machine() during modprobe aes (was Re: Another AR5008 hang)
Date: Thu, 15 Apr 2010 17:22:05 -0400 [thread overview]
Message-ID: <20100415172205.c1e57636.akpm@linux-foundation.org> (raw)
In-Reply-To: <4bbb7896.48c3f10a.30b9.365b@mx.google.com>
On Tue, 06 Apr 2010 11:08:22 -0700 (PDT) Ben Gamari <bgamari.foss@gmail.com> wrote:
>
> ...
>
> I just built 2.6.34-rc3 with the appropriate fixes for the ACPI thermal lockdep
> issues and have attached the dmesg output of the crash below. It appears that
> modprobe is freezing with a few locks held while inserting aes.ko. In
> particular, it seems that the kernel is deadlocking inside of stop_machine()
> while flushing workqueues.
>
> ...
>
My guess would be that ieee80211 is calling crypto->request_module()
under rtnl_lock, and the fact that rtnl_lock is held is causing
modprobe->stop_machine to not complete.
> P.S. I am now quite certain that I was mistaken in saying that 2.6.33 was
> affected. This seems to just be a 2.6.34 issue.
OK, thanks, I'll ask Rafael and Maciej to track this as a post-2.6.33
regression, probably wireless.
next prev parent reply other threads:[~2010-04-16 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 17:26 Another AR5008 hang Ben Gamari
2010-03-30 6:03 ` Johannes Berg
2010-03-30 13:14 ` Ben Gamari
2010-03-30 17:33 ` Ben Gamari
2010-04-06 18:08 ` Lockup inside of stop_machine() during modprobe aes (was Re: Another AR5008 hang) Ben Gamari
2010-04-11 16:47 ` [REGRESSION] " Ben Gamari
2010-04-15 21:22 ` Andrew Morton [this message]
2010-04-16 1:15 ` Ben Gamari
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=20100415172205.c1e57636.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ath9k@venema.h4ckr.net \
--cc=bgamari.foss@gmail.com \
--cc=herbert@gondor.hengli.com.au \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).