linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath9k very unstable and kills file-system.
Date: Fri, 19 Nov 2010 17:13:05 -0800	[thread overview]
Message-ID: <4CE720A1.3090408@candelatech.com> (raw)

It's been another frustrating week for using ath9k.

With a patched wpa_supplicant (found here:
https://github.com/greearb/hostap-ct/tree/)
I can reliably cause ath9k to spew all sorts of DMA warnings
and evidently crash the hard-drive controller and/or corrupt the
file system so bad that fsck cannot fix it.  (Back up anything you
want to keep before attempting to reproduce this.)

The test case is simply create 30 or so STA interfaces, run one instance
of the patched wpa_supplicant to control the 30 interfaces, and send
a bit of traffic across the interfaces.  It's not even needed to send
any significant data...probably just the supplicant associate logic
is enough.

You'll want the xmit locking patch Felix posted or it will likely spew
lockdep warnings and/or lockup before it gets a chance to crash your
hard drive.

There are no other /n NICs that can do virtual stations, so I must
either get ath9k functional or give up on that feature set entirely.

If anyone wants to help with this and cannot easily reproduce it,
please let me know and I'll furnish scripts etc to make it easier
to reproduce.

I'm also happy to help test patches.

Thanks,
Ben

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


             reply	other threads:[~2010-11-20  1:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20  1:13 Ben Greear [this message]
2010-11-20  2:25 ` ath9k very unstable and kills file-system Luis R. Rodriguez
2010-11-20  2:44 ` Felix Fietkau
2010-11-20 17:34 ` Björn Smedman

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=4CE720A1.3090408@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.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).