linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [RFC] ath9k:  Detect and work-around tx-queue hang.
Date: Fri, 22 Feb 2013 10:19:26 +0530	[thread overview]
Message-ID: <20774.63702.208829.602903@gargle.gargle.HOWL> (raw)
In-Reply-To: <5126F732.6040007@candelatech.com>

Ben Greear wrote:
> I'll be happy to test patches, but I'm not sure how to go about
> debugging the real problem on my own.  Maybe some stats could
> be added to the xmit debugfs file to help diagnose the problem,
> or maybe some other debugfs info will help?
> 
> I can't reproduce the problem with ath9k debugging set at the
> previous suggested level, so it would have to be something
> less invasive.
> 
> As for just stations going out of range, it remains locked up
> even with signal level goes back to -20, so it's not just a simple
> station-out-of range issues..

Sure, but I think that filtered frames are not handled properly,
especially with aggregation, since the debugfs stats from your earlier email
showed a large counter (from a private patch ?):

TXERR Filtered:            224          0         0         0

Sujith

  reply	other threads:[~2013-02-22  4:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22  2:06 [RFC] ath9k: Detect and work-around tx-queue hang greearb
2013-02-22  4:28 ` Sujith Manoharan
2013-02-22  4:42   ` Ben Greear
2013-02-22  4:49     ` Sujith Manoharan [this message]
2013-02-22  5:26       ` Ben Greear
2013-02-22 11:36         ` [ath9k-devel] " Felix Fietkau
2013-02-22 12:25           ` Sujith Manoharan
2013-02-22 12:38             ` Felix Fietkau
2013-02-22 12:55               ` Ben Greear
2013-03-12 18:16                 ` Ben Greear
2013-03-13 14:14                   ` Sujith Manoharan
2013-03-13 14:18                   ` Felix Fietkau

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=20774.63702.208829.602903@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=ath9k-devel@venema.h4ckr.net \
    --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).