Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-issue with stop RX/TX DMA - correlation with WMM traffic classes?
Date: Fri, 12 Apr 2013 22:49:32 +0200	[thread overview]
Message-ID: <5168735C.8050901@openwrt.org> (raw)
In-Reply-To: <3A974E27-70CF-4240-BC95-66166A2AAD7D@stephan.homeunix.net>

On 2013-04-12 6:57 PM, Jan L?hr wrote:
> Hallo Felix,
> 
> Am 12.04.2013 um 17:41 schrieb Felix Fietkau:
>> On 2013-04-12 10:27 AM, Rougu wrote:
>>> while I might be totally wrong with my observation, I still would like 
>>> to share it, because this issue is lingering for years now and many 
>>> users are waiting to a solid grip on it to fix it.
>>> 
>>> I'm running several freifunk-nodes in Cologne, Germany, where the 
>>> firmware contains a ath9k-watchdog that restarts the node, once the 
>>> failure occurs. One of my nodes is affected in varying intervals of 200 
>>> .. 10000 seconds uptime, depending on WLAN activity.
>>> 
>>> (openwrt, attitude adjustment, kernel 3.3.8)
>> Please also run a test with OpenWrt trunk and compare stability.
> 
> thanks for providing feedback on this issue. Please keep in mind
> that using OpenWRT-trunk is not that easy for node operators of freifunk
> networks. I hope Rouge is able to do so - at least we will provide help
> in our Freifunk-Community (kbu).
I'm also considering backporting mac80211 from trunk to AA after the
release (meant for people that build the branch from source, not for a
follow-up release).

> I'd really like to discuss this issue at the upcoming Wireless
> Community Weekend in Berlin - will I meet you there?
Yes, definitely.

> At the moment we really do suffer from excessive driver-woos -
> causing the need to reboot nodes:
> ~ 1450 incidents have been reported within one month
> (http://register.kbu.freifunk.net/watchdog_bites). Some nodes are almost
> DoS'ed by certain - yet undiscovered - clients.
I'm really interested how such a setup behaves with either trunk or a
mac80211 backport to AA. Many fixes were added that could not easily be
backported to AA because they were too intrusive for the release.

- Felix

      reply	other threads:[~2013-04-12 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  8:27 [ath9k-devel] ath9k-issue with stop RX/TX DMA - correlation with WMM traffic classes? Rougu
2013-04-12 15:41 ` Felix Fietkau
2013-04-12 16:57   ` Jan Lühr
2013-04-12 20:49     ` Felix Fietkau [this message]

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=5168735C.8050901@openwrt.org \
    --to=nbd@openwrt.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox