All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:41:27 -0700	[thread overview]
Message-ID: <4CAA1FD7.6030209@candelatech.com> (raw)
In-Reply-To: <AANLkTimzuUxvRFDwiJNyi2P2Yd-gK9gSoDVfd72eUxVa@mail.gmail.com>

On 10/04/2010 10:51 AM, Luis R. Rodriguez wrote:
> On Mon, Oct 4, 2010 at 10:48 AM, Ben Greear<greearb@candelatech.com>  wrote:

>> 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).
>
> ath5k has no power save support.
>
>> 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.
>
> Try:
>
> iw dev wlan0 dev set power_save off
>
> for each wireless interface and see if you see these go away.

That seems to be helping...most of the interfaces won't actually
associate (probes to AP time-out and such), but at least it isn't
crashing so often.

Should we always disable power-save if there are > 1 VIF?

Thanks,
Ben

>
>    Luis


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2010-10-04 18:41 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
2010-10-04 17:51           ` Luis R. Rodriguez
2010-10-04 18:41             ` Ben Greear [this message]
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=4CAA1FD7.6030209@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.