Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:41749 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750870Ab1I2Kdn (ORCPT ); Thu, 29 Sep 2011 06:33:43 -0400 Received: by gyg10 with SMTP id 10so380487gyg.19 for ; Thu, 29 Sep 2011 03:33:42 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20110830064137.GA4719@ecki> <14be9f3b-4c91-481d-9e52-f3119659fd59@email.android.com> <20110927214245.GA1416@ecki> Date: Thu, 29 Sep 2011 18:33:42 +0800 Message-ID: (sfid-20110929_123356_162506_D20DF93F) Subject: Re: ath9k: irq storm after suspend/resume From: Adrian Chadd To: Mohammed Shafi Cc: Clemens Buchacher , linux-wireless@vger.kernel.org, beta992@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hm, Has someone figured out which ISR bits are being triggered? If not, I can likely whip up a patch which adds some relevant printk's. I think it's worth establishing: * is it a sync/async interrupt; * is it a fatal interrupt (eg something like a PCI bus error or transaction timeout) or is it a normal ISR bit that keeps firing; * .. and which one is firing. Adrian