From: Clemens Buchacher <drizzd@aon.at>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: irq storm after suspend/resume
Date: Fri, 21 Oct 2011 22:20:38 +0200 [thread overview]
Message-ID: <20111021202038.GA1523@ecki.lan> (raw)
In-Reply-To: <CAJ-Vmonaec_i5d_LGupY5uwzMUn3CzNn-rGSh6oqLOHc8ewFVg@mail.gmail.com>
On Fri, Oct 21, 2011 at 10:10:21PM +0800, Adrian Chadd wrote:
>
> I assume you have disabled the NIC power save option. Not just APSM,
> etc, but the powersave options in iw. I don't know what they are,
> sorry, only that they exist.
I am not sure if that's what you mean, but if I set "iwconfig wlan0
power off" it makes no difference.
> I suggest modifying ath_intr() so if there is an interrupt storm,
> disable _all_ sources of interrupts (ie, set sync_cause, async_cause
> to 0, set imr to 0, set ier to 0) and see if it continues occuring.
They keep coming with this too.
> If the interrupt storm continue occuring, try putting the whole NIC to
> sleep entirely (ie, call pcipowersave to put the NIC to sleep, then
> make sure the NIC -stays- asleep somehow, ie so nothing else tries
> waking it up - I don't know how to do this, likely you'll have to
> clear some interface flag so the rest of the ath9k and 802.11 stack
> thinks the nic is actually down for the count) and see if you're still
> getting spurious interrupts.
I am now calling
ath9k_hw_ops(sc->sc_ah)->config_pci_powersave(sc->sc_ah, true);
ath9k_setpower(sc, ATH9K_PM_FULL_SLEEP);
right before request_irq, and the interrupts still come. And the
device is in FULL_SLEEP the whole time, at least according to
ah->power_mode.
Clemens
WARNING: multiple messages have this Message-ID (diff)
From: Clemens Buchacher <drizzd@aon.at>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
linux-wireless@vger.kernel.org,
ath9k-devel <ath9k-devel@lists.ath9k.org>
Subject: Re: ath9k: irq storm after suspend/resume
Date: Fri, 21 Oct 2011 22:20:38 +0200 [thread overview]
Message-ID: <20111021202038.GA1523@ecki.lan> (raw)
In-Reply-To: <CAJ-Vmonaec_i5d_LGupY5uwzMUn3CzNn-rGSh6oqLOHc8ewFVg@mail.gmail.com>
On Fri, Oct 21, 2011 at 10:10:21PM +0800, Adrian Chadd wrote:
>
> I assume you have disabled the NIC power save option. Not just APSM,
> etc, but the powersave options in iw. I don't know what they are,
> sorry, only that they exist.
I am not sure if that's what you mean, but if I set "iwconfig wlan0
power off" it makes no difference.
> I suggest modifying ath_intr() so if there is an interrupt storm,
> disable _all_ sources of interrupts (ie, set sync_cause, async_cause
> to 0, set imr to 0, set ier to 0) and see if it continues occuring.
They keep coming with this too.
> If the interrupt storm continue occuring, try putting the whole NIC to
> sleep entirely (ie, call pcipowersave to put the NIC to sleep, then
> make sure the NIC -stays- asleep somehow, ie so nothing else tries
> waking it up - I don't know how to do this, likely you'll have to
> clear some interface flag so the rest of the ath9k and 802.11 stack
> thinks the nic is actually down for the count) and see if you're still
> getting spurious interrupts.
I am now calling
ath9k_hw_ops(sc->sc_ah)->config_pci_powersave(sc->sc_ah, true);
ath9k_setpower(sc, ATH9K_PM_FULL_SLEEP);
right before request_irq, and the interrupts still come. And the
device is in FULL_SLEEP the whole time, at least according to
ah->power_mode.
Clemens
next prev parent reply other threads:[~2011-10-21 20:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 11:32 ath9k: irq storm after suspend/resume Clemens Buchacher
2011-08-29 7:55 ` Mohammed Shafi
2011-08-29 11:53 ` Mohammed Shafi
2011-08-29 15:12 ` Mohammed Shafi
2011-08-30 6:41 ` Clemens Buchacher
2011-08-30 9:33 ` Mohammed Shafi
2011-08-30 9:41 ` Mohammed Shafi
2011-09-01 6:24 ` Clemens Buchacher
2011-09-26 9:24 ` Mohammed Shafi
2011-09-27 21:42 ` Clemens Buchacher
2011-09-29 8:18 ` Mohammed Shafi
2011-09-29 10:33 ` Adrian Chadd
2011-09-29 17:11 ` Clemens Buchacher
[not found] ` <CAD2nsn0Z2J4r4tN_fLjx5bbvz2bg6NVcQ8vppJbbNcgOF8pFew@mail.gmail.com>
[not found] ` <CAJ-VmokcM4KmzV7Rn9PA68iEiTJiPw=ffYgNFLDAHShxD0HNAg@mail.gmail.com>
2011-10-03 8:48 ` Clemens Buchacher
2011-10-04 7:58 ` Adrian Chadd
2011-10-04 18:15 ` Clemens Buchacher
2011-10-04 21:11 ` Adrian Chadd
2011-10-05 6:28 ` Clemens Buchacher
2011-10-05 13:02 ` Adrian Chadd
2011-10-12 13:10 ` Mohammed Shafi
2011-10-15 9:39 ` Clemens Buchacher
2011-10-15 10:01 ` Adrian Chadd
2011-10-18 6:44 ` Clemens Buchacher
2011-10-18 7:05 ` Adrian Chadd
2011-10-21 10:22 ` Clemens Buchacher
2011-10-21 14:10 ` [ath9k-devel] " Adrian Chadd
2011-10-21 14:10 ` Adrian Chadd
2011-10-21 19:03 ` [ath9k-devel] " Clemens Buchacher
2011-10-21 19:03 ` Clemens Buchacher
2011-10-21 20:20 ` Clemens Buchacher [this message]
2011-10-21 20:20 ` Clemens Buchacher
2011-10-22 0:47 ` [ath9k-devel] " Adrian Chadd
2011-10-22 0:47 ` Adrian Chadd
2011-10-22 7:22 ` [ath9k-devel] " Clemens Buchacher
2011-10-22 7:22 ` Clemens Buchacher
2011-10-22 7:29 ` [ath9k-devel] " Adrian Chadd
2011-10-22 7:29 ` Adrian Chadd
2011-10-04 18:36 ` Clemens Buchacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111021202038.GA1523@ecki.lan \
--to=drizzd@aon.at \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.