Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Dave Taht <dave.taht@gmail.com>, Sebastian Moeller <moeller0@gmx.de>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [ath9k-devel] periodic hang of ath9k
Date: Sun, 13 Jul 2014 12:44:38 -0700	[thread overview]
Message-ID: <53C2E1A6.1070001@candelatech.com> (raw)
In-Reply-To: <CAA93jw7DyKexOwqFBnT_1Z1REXi0UV8JtzPMC7WmQUGOx_+UXg@mail.gmail.com>

On 07/13/2014 12:18 PM, Dave Taht wrote:
> cc-ing ath9k-devel for this update on http://www.bufferbloat.net/issues/442
>
> this bug, which some people (usually on macs with low signal strength)
> can get to occur fairly rapidly, but I can't, is driving me 9 kinds of
> crazy...

I've mentioned this before..but I have a patch that works around this
problem:

I had merge issues, so now it's two patches until I have time to clean up
my tree:

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.14.dev.y/.git;a=commit;h=579035d4b2b7110d67ff451e728709f5b2510ca0

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.14.dev.y/.git;a=commit;h=ae6f95e8a35578e0668e47becb053b29009eec9a

I suspect this may cause memory leaks, as a test that causes these work-arounds to hit
often will run out of memory after a few days (200+ station vifs constantly doing traffic).
Could be lots of other code of course, and kmemleak shows no leaks, so I'm at a loss on
the mem leak issue.

If you can, try patching these in and see if that works around your tx hang problem.

I'd love to have a better fix, btw.

Thanks,
Ben


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


  reply	other threads:[~2014-07-13 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 19:18 [Cerowrt-devel] " Dave Taht
2014-07-13 19:44 ` Ben Greear [this message]
2014-07-14  4:25 ` Sujith Manoharan
2014-07-14 10:48   ` [Cerowrt-devel] [ath9k-devel] " Felix Fietkau
2014-07-14 18:51 ` [Cerowrt-devel] " Stephen Hemminger
2014-07-14 23:02   ` R.

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53C2E1A6.1070001@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=moeller0@gmx.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