Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:61230 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404Ab1JVAre (ORCPT ); Fri, 21 Oct 2011 20:47:34 -0400 Received: by gyb13 with SMTP id 13so4352651gyb.19 for ; Fri, 21 Oct 2011 17:47:33 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20111021202038.GA1523@ecki.lan> References: <20111005062528.GA1403@ecki> <20111015093902.GA23520@ecki> <20111018064459.GA1442@ecki> <20111021102221.GA1463@ecki.lan> <20111021202038.GA1523@ecki.lan> Date: Sat, 22 Oct 2011 08:47:33 +0800 Message-ID: (sfid-20111022_024744_445042_1BA71901) Subject: Re: ath9k: irq storm after suspend/resume From: Adrian Chadd To: Clemens Buchacher Cc: Mohammed Shafi , linux-wireless@vger.kernel.org, ath9k-devel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: .. then I don't think it's specifically the NIC. >From what I understand, unless there are bus errors happening (and that'd occur with the NIC awake or having something being written to it) the NIC shouldn't be generating interrupts if: * sync/async cause are 0; * ier is 0; * imr is 0. Now maybe some part of ath9k is still trying to write to the NIC when it's asleep, but it would set some bits in sync_cause/async_cause. At this point I'd really suggest whacking other devices into the slot to see if they generate the same kind of behaviour. Adrian