linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Any /n NICs that support APs and multiple STAs other than ath9k?
Date: Wed, 06 Oct 2010 11:49:28 -0700	[thread overview]
Message-ID: <4CACC4B8.7040500@candelatech.com> (raw)
In-Reply-To: <AANLkTimB7=odPK3qTAhFBdzaMFFGVar0kyMrb-p9SgYy@mail.gmail.com>

On 10/06/2010 11:45 AM, Luis R. Rodriguez wrote:
> On Wed, Oct 6, 2010 at 9:29 AM, Ben Greear<greearb@candelatech.com>  wrote:
>> I would like to have a different hardware/driver combination to try
>> to tie-break whether bugs are in mac80211 or in the ath9k driver/hardware.
>>
>> I don't mind doing a bit of driver hacking so long as the basic support
>> is there (I think it's mostly the ability to set a BSSID mask and rxfilter
>> accordingly).
>
> Your best bet is to test against mac80211_hwsim, that would rule out
> any hardware. I think Jouni and Johannes have also a way to get the
> devices to talk to each other. Perhaps some documentation of that on
> the kernel Documentation/networking/mac80211_hwsim/

Ok.  I'm trying to hack slub to give me a better stack trace of where
the skb was deleted.  If that doesn't turn up anything obvious, then
I'll go read up on hwsim.

Are you aware of any DMA issues that might cause ath9k to write into
places it should not?  Previously, I've seen a lot of errors in
the logs about ath9k not being able to stop DMA in time, but I haven't
seen those while reproducing the memory corruption.


Thanks,
Ben

>
>    Luis


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


  parent reply	other threads:[~2010-10-06 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 16:29 Any /n NICs that support APs and multiple STAs other than ath9k? Ben Greear
2010-10-06 18:45 ` Luis R. Rodriguez
2010-10-06 18:48   ` Johannes Berg
2010-10-06 18:51     ` Ben Greear
2010-10-06 18:49   ` Ben Greear [this message]
2010-10-06 18:58     ` Luis R. Rodriguez
2010-10-06 19:08       ` Ben Greear
2010-10-06 19:21         ` 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=4CACC4B8.7040500@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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).