From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-yw0-f46.google.com ([209.85.213.46]:39321 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751964Ab1JVH3m (ORCPT ); Sat, 22 Oct 2011 03:29:42 -0400 Received: by ywm3 with SMTP id 3so228098ywm.19 for ; Sat, 22 Oct 2011 00:29:42 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20111022072215.GA2524@ecki> References: <20111015093902.GA23520@ecki> <20111018064459.GA1442@ecki> <20111021102221.GA1463@ecki.lan> <20111021202038.GA1523@ecki.lan> <20111022072215.GA2524@ecki> Date: Sat, 22 Oct 2011 15:29:42 +0800 Message-ID: (sfid-20111022_092946_212519_17ABD172) 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: On 22 October 2011 15:22, Clemens Buchacher wrote: > Looks like you had it right from the start. After unloading the jme > module [*1*] I cannot reproduce the IRQ storm any more. From > looking at dmesg it should have been obvious, since it also gets > IRQ 17 assigned. I don't know how I missed that, I was sure I had > checked. > > Sorry guys, for most likely wasting your time. And thanks for your > patience. Ah, eek! Well, you're welcome! And I hope you/others have a better understanding of how the interrupt setup on these NICs work. (I certainly have a better understanding now of the host interface and what we can poke when it's awake and asleep.) Good luck! Adrian From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Chadd Date: Sat, 22 Oct 2011 15:29:42 +0800 Subject: [ath9k-devel] ath9k: irq storm after suspend/resume In-Reply-To: <20111022072215.GA2524@ecki> References: <20111015093902.GA23520@ecki> <20111018064459.GA1442@ecki> <20111021102221.GA1463@ecki.lan> <20111021202038.GA1523@ecki.lan> <20111022072215.GA2524@ecki> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 22 October 2011 15:22, Clemens Buchacher wrote: > Looks like you had it right from the start. After unloading the jme > module [*1*] I cannot reproduce the IRQ storm any more. From > looking at dmesg it should have been obvious, since it also gets > IRQ 17 assigned. I don't know how I missed that, I was sure I had > checked. > > Sorry guys, for most likely wasting your time. And thanks for your > patience. Ah, eek! Well, you're welcome! And I hope you/others have a better understanding of how the interrupt setup on these NICs work. (I certainly have a better understanding now of the host interface and what we can poke when it's awake and asleep.) Good luck! Adrian