From: Ben Gamari <bgamari.foss@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath9k@venema.h4ckr.net
Subject: Re: [REGRESSION] Lockup inside of stop_machine() during modprobe aes (was Re: Another AR5008 hang)
Date: Sun, 11 Apr 2010 09:47:05 -0700 (PDT) [thread overview]
Message-ID: <4bc1fd09.9615f10a.46f6.ffffab58@mx.google.com> (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:
> Hey all,
>
> 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.
>
I can confirm that modprobing aes explicitly also results in the stop_machine()
deadlock, so this doesn't appear to be an interaction with ath9k or the
mac80211 subsystem.
Furthermore, if I disable CONFIG_CRYPTO_AES_X86_64 (I'm on a Core Duo
platform), aes loads as expected and things work as they should.
Any ideas? I'm rather disturbed that this regression has still not had a single
reply while -rc4 is so near.
- Ben
next prev parent reply other threads:[~2010-04-11 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4bb0e2da.04c2f10a.32b2.11ae@mx.google.com>
[not found] ` <1269928986.3927.5.camel@jlt3.sipsolutions.net>
[not found] ` <4bb1f940.47c2f10a.3469.609b@mx.google.com>
[not found] ` <4bb235fb.0baa660a.5b56.ffffa9c2@mx.google.com>
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 ` Ben Gamari [this message]
2010-04-15 21:22 ` Andrew Morton
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=4bc1fd09.9615f10a.46f6.ffffab58@mx.google.com \
--to=bgamari.foss@gmail.com \
--cc=ath9k@venema.h4ckr.net \
--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