public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: Simon Wunderlich <sw@simonwunderlich.de>,
	Sven Eckelmann <sven@narfation.org>,
	b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [batman-adv] Deaf hang happens quite often for a distant node (ar9331 + openwrt)
Date: Sun, 23 Apr 2017 10:49:37 +0800	[thread overview]
Message-ID: <42b14dc4-e931-527f-e105-07db7c6f3b87@gmail.com> (raw)

Hi Simon and Sven,

Thank you very much for your help.

I hope I correctly took the deaf state and 0xdeadbeef patches:
[1] https://patchwork.kernel.org/patch/9433619/
[2] https://patchwork.kernel.org/patch/9433621/

Also, I use software encryption, in the hope to avoid key cache corruption.
[3] https://patchwork.kernel.org/patch/9381651/

Are there other patches I need to apply for ar9331?

I use ath_warn() before some cases of ath9k_queue_reset(). For a distant 
node, I saw below. deaf hang comes quite often, did you observe this too?
-----------------
[  985.520000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 1166.000000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 1617.200000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 2399.280000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 4023.600000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 4648.610000] ath: phy0: tx hung, resetting the chip
[ 4802.610000] ath: phy0: tx hung, resetting the chip
[ 5103.360000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 5975.680000] ath: phy0: RX deaf hang is detected. Schedule chip reset
[ 6998.400000] ath: phy0: RX deaf hang is detected. Schedule chip reset
-----------------

Thanks.

Xuebing Wang


                 reply	other threads:[~2017-04-23  2:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42b14dc4-e931-527f-e105-07db7c6f3b87@gmail.com \
    --to=xbing6@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /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