From: Bruno Randolf <br1@einfach.org>
To: Bruno Randolf <br1@einfach.org>,
Oleksij Rempel <linux@rempel-privat.de>,
linux-wireless@vger.kernel.org, nbd@openwrt.org,
sujith@msujith.org
Cc: Ingo Randolf <ingo.randolf@qupik.com>
Subject: Re: ath9k AR9287 status?
Date: Thu, 03 Oct 2013 18:05:32 +0100 [thread overview]
Message-ID: <524DA3DC.6060806@einfach.org> (raw)
In-Reply-To: <5249A2F7.5090908@einfach.org>
On 09/30/2013 05:12 PM, Bruno Randolf wrote:
> On 09/30/2013 02:27 PM, Oleksij Rempel wrote:
>>>> Check:
>>>> - PCIe related power managment - ASPM.
>
> Hmm, disabling ASPM in the BIOS and per kernel command line
> (pcie_aspm=off) did not help.
>
>> I use 3.11 right now. In case of PCIe issue, backport wont help you.
>> Test completely new kernel.
>
> I'll try 3.11 later.
I just tried current wireless-testing (3.12.0-rc3-wl) and it shows the
same problems.
For reference:
Card: Unex DNXA-97 (AR9287) http://unex.com.tw/product/dnxa-97
Board: Advantech MIO-2261N (Atom N260)
ASPM is disabled in the BIOS and by pcie_aspm=off. Scanning seems to
work, but when I start up hostapd (v2.0, simple AP config) nothing
happens (no AP is found by clients). When I stop hostapd the system
freezes with "BUG: soft lockup - CPU#3 stuck for 23s! (hostapd:2250)"
bruno
next prev parent reply other threads:[~2013-10-03 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 8:00 ath9k AR9287 status? Bruno Randolf
2013-09-30 9:28 ` Oleksij Rempel
2013-09-30 10:38 ` Bruno Randolf
2013-09-30 13:27 ` Oleksij Rempel
2013-09-30 16:12 ` Bruno Randolf
2013-10-03 17:05 ` Bruno Randolf [this message]
2013-10-17 2:08 ` Sujith Manoharan
2013-11-13 16:37 ` ath9k AR9382 high latency ping Bruno Randolf
2013-11-14 9:23 ` Bruno Randolf
2013-11-14 10:25 ` Felix Fietkau
2013-11-14 17:38 ` Bruno Randolf
2013-11-19 16:46 ` ath9k AR9382 high latency ping (solved) Bruno Randolf
2013-09-30 18:10 ` ath9k AR9287 status? Weedy
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=524DA3DC.6060806@einfach.org \
--to=br1@einfach.org \
--cc=ingo.randolf@qupik.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=nbd@openwrt.org \
--cc=sujith@msujith.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).