From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:63400 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753583Ab1H2PMf (ORCPT ); Mon, 29 Aug 2011 11:12:35 -0400 Received: by wyg24 with SMTP id 24so4147459wyg.19 for ; Mon, 29 Aug 2011 08:12:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20110827113253.GA1444@ecki> Date: Mon, 29 Aug 2011 20:42:33 +0530 Message-ID: (sfid-20110829_171239_267644_F517D296) Subject: Re: ath9k: irq storm after suspend/resume From: Mohammed Shafi To: Clemens Buchacher Cc: 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: >>> But still, the interrupts come. Note that according to >>> /proc/interrupts, the IRQ line is not shared with any other device. >>> I did not manage to determine which interrupt it is exactly, >>> because the device is not in a ready state (SC_OP_INVALID is set) >>> when they happen (in either scenario that triggers the IRQ storm). >>> And SC_OP_INVALID is cleared only much later in ath9k_start. >>> >>> So, I am at a loss. Any ideas? >> >> please provide the lspci -vvvxx. >> also looking at >> /sys/kernel/debug/ieee80211/phy0/ath9k$ sudo cat interrupt. > > hi, i think this will help, please get the message sudo modprobe ath9k > debug=0xffffffff. > few fatal PCI interrupt messages are based on ATH_DEBUG_ANY. > thanks. > we can also try to disable MIB interrupts though its handled properly now in ath9k http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/ath9k/2008-09-25/0001-ath9k-disable-MIB-interrupts-to-fix-interrupt-storm.patch -- shafi