From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Gamari <bgamari.foss@gmail.com>
Date: Wed, 07 Apr 2010 09:00:48 -0700 (PDT)
Subject: [ath9k-devel] [REGRESSION,
	2.6.34-rc1] Lockup inside of stop_machine() during modprobe aes
	(was	Re: Another AR5008 hang)
In-Reply-To: <4bbb7896.48c3f10a.30b9.365b@mx.google.com>
References: <4bb0e2da.04c2f10a.32b2.11ae@mx.google.com>
	<1269928986.3927.5.camel@jlt3.sipsolutions.net>
	<4bb1f940.47c2f10a.3469.609b@mx.google.com>
	<4bb235fb.0baa660a.5b56.ffffa9c2@mx.google.com>
	<4bbb7896.48c3f10a.30b9.365b@mx.google.com>
Message-ID: <4bbcac30.9915f10a.0846.ffffe55a@mx.google.com>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

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.
> 
Just in case this wasn't clear, this issue is a regression from 2.6.33 and
ought to be added to the appropriate tracking list.

Thanks,

- Ben