linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Felix Fietkau <nbd@openwrt.org>,
	Luis Rodriguez <Luis.Rodriguez@atheros.com>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] Script to crash ath9k with DMA errors.
Date: Mon, 06 Dec 2010 12:22:26 -0800	[thread overview]
Message-ID: <4CFD4602.1030304@candelatech.com> (raw)
In-Reply-To: <AANLkTingy7fPH14hW_mg8_YcotX29pYCu910Gw48grrD@mail.gmail.com>

On 12/06/2010 12:11 PM, Björn Smedman wrote:
> On Mon, Dec 6, 2010 at 8:47 PM, Ben Greear<greearb@candelatech.com>  wrote:
>> With 16 properly configured non-encrypted stations, running with
>> wpa-supplicant
>> with netlink driver&  sharing scan results,  the interfaces quickly
>> associate.
>>
>> However, I do continue to see DMA warnings such as these (I had picked up my
>> portable phone, and it knocked all the interfaces offline ..here
>> they are coming back up after I hung up the phone).
>
> Is there some theory as to why using multiple interfaces cause so many
> problems with DMA?

Seems pretty directly related to channel changes and/or resets, and exacerbated
by other interfaces sending data while another is scanning, for instance.

Other issues we've found in the past have been various races that you wouldn't
normally see with a single VIF.

Thanks,
Ben

>
> /Björn


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

  reply	other threads:[~2010-12-06 20:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  0:28 Script to crash ath9k with DMA errors Ben Greear
2010-11-30  0:44 ` [ath9k-devel] " Luis R. Rodriguez
2010-11-30  0:52   ` Ben Greear
2010-12-01 23:22   ` Ben Greear
2010-12-03  8:14     ` Ben Greear
2010-12-05  2:41       ` Felix Fietkau
2010-12-05  3:30         ` Ben Greear
2010-12-05  5:18         ` Ben Greear
2010-12-06 19:36           ` Luis R. Rodriguez
2010-12-06 19:47             ` Ben Greear
2010-12-06 19:53               ` Luis R. Rodriguez
2010-12-06 19:53                 ` Luis R. Rodriguez
2010-12-06 20:28                   ` Ben Greear
2010-12-06 20:38                     ` Felix Fietkau
2010-12-06 20:11               ` Björn Smedman
2010-12-06 20:22                 ` Ben Greear [this message]
2010-12-06 20:42                   ` Luis R. Rodriguez
2010-12-06 21:00                     ` Ben Greear
2010-12-06 21:16                       ` 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=4CFD4602.1030304@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=bjorn.smedman@venatech.se \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=nbd@openwrt.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).