From: Felix Fietkau <nbd@openwrt.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k very unstable and kills file-system.
Date: Sat, 20 Nov 2010 03:44:27 +0100 [thread overview]
Message-ID: <4CE7360B.7090700@openwrt.org> (raw)
In-Reply-To: <4CE720A1.3090408@candelatech.com>
On 2010-11-20 2:13 AM, Ben Greear wrote:
> 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 rx dma warnings went away on my devices with my patch
"ath9k: fix timeout on stopping rx dma"
Please try that one and see if it helps with your corruption issues.
- Felix
next prev parent reply other threads:[~2010-11-20 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 1:13 ath9k very unstable and kills file-system Ben Greear
2010-11-20 2:25 ` Luis R. Rodriguez
2010-11-20 2:44 ` Felix Fietkau [this message]
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=4CE7360B.7090700@openwrt.org \
--to=nbd@openwrt.org \
--cc=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).