From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Ath9k in funky state after adding 130 STA interfaces.
Date: Mon, 04 Oct 2010 10:48:36 -0700 [thread overview]
Message-ID: <4CAA1374.1040707@candelatech.com> (raw)
In-Reply-To: <20101004172827.GM2105@tux>
On 10/04/2010 10:28 AM, Luis R. Rodriguez wrote:
> On Mon, Oct 04, 2010 at 10:24:21AM -0700, Peter Stuge wrote:
>> Ben Greear wrote:
>>> I was hoping the 'deadbeef' registers indicated a particular error
>>> in the NIC that I might could use for further debugging.
>>
>> I'd guess it's a general error rather than something specific. I get
>> it on most boots and the driver needs some jerking around before the
>> card will start working. Sometimes it doesn't matter what I do and
>> power cycle is all that seems to help. I haven't spent much time on
>> thorough research yet though, in part because there's so little
>> response here. :\
>
> yeah the deadbeef stuff typically is a misprogramming on the
> driver to not wake the chip up for a read/write operation.
> We have a lot of fixes for this over the last few kernels
> and if you using 2.6.35 chances are a few fixes may not
> have trickled down yet. For development purposes you are
> best to use the latest always.
I'm on wireless-testing, totally up-to-date as I can get.
It seems trivial to kill the system using lots of STA devices on ath9k,
so if anyone needs help reproducing this, I'm more than happy
to help. In general, I'd guess that the problems I hit very quickly
could also be hit by other users if they got unlucky, so it may
be worth some time to debug this in detail.
Basically, create 130 (don't think exact number matters) STA
devices, configure a wpa_supplicant for each, and stand back
and watch things go south.
I do have a few extra patches..like to restrict scanning to
the single associated channel, but I doubt that has much
impact on the bug (and it works fine in ath5k).
I have lockdep turned on, and pre-empt enabled in the kernel
configs.
If someone prefers, I can make my entire tree available through
git and post .config files, etc.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-10-04 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 5:19 [ath9k-devel] Ath9k in funky state after adding 130 STA interfaces Ben Greear
2010-10-04 17:07 ` Luis R. Rodriguez
2010-10-04 17:09 ` Peter Stuge
2010-10-04 17:21 ` Luis R. Rodriguez
2010-10-04 17:21 ` Luis R. Rodriguez
2010-10-04 17:24 ` Ben Greear
2010-10-04 17:24 ` Ben Greear
2010-10-04 17:18 ` Ben Greear
2010-10-04 17:24 ` Peter Stuge
2010-10-04 17:28 ` Luis R. Rodriguez
2010-10-04 17:48 ` Ben Greear [this message]
2010-10-04 17:51 ` Luis R. Rodriguez
2010-10-04 18:41 ` Ben Greear
2010-10-04 20:32 ` Luis R. Rodriguez
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=4CAA1374.1040707@candelatech.com \
--to=greearb@candelatech.com \
--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.