From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mihai Moldovan <ionic@ionic.de>
Date: Thu, 12 Jan 2012 21:56:58 +0100
Subject: [ath9k-devel] Kernel panic with AR9485 and kernel 3.1.6
In-Reply-To: <CAJ-Vmok9WGSjQV6wKtTy4oAoXwn8Q4T6-HNkcW992TYhUMrpQA@mail.gmail.com>
References: <CAFopJHdY+gfb0EFC-sxsdj-20LN=qBasB-pw2Tejt-NRgFghUw@mail.gmail.com>
	<4F0F3C45.6020107@ionic.de>
	<CAJ-Vmok9WGSjQV6wKtTy4oAoXwn8Q4T6-HNkcW992TYhUMrpQA@mail.gmail.com>
Message-ID: <4F0F491A.1010407@ionic.de>
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

Hm, shouldn't the kernel actually detect something like this (i.e.,
detect when it's running in kernel mode for too long and not letting
userspace processes run)?


* On 12.01.2012 09:51 PM, Adrian Chadd wrote:
> Remember, kim though it was a hang until we enabled some ath9k
> debugging. We then discovered the driver was sitting in a very tight
> interrupt handling loop...
>
>
>
> adrian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4369 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120112/28bf8bb3/attachment-0001.bin