Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Loganaden Velvindron <loganaden@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Dave Taht <dave.taht@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] crypto-fq bug postmortem is up
Date: Mon, 19 Sep 2016 07:56:39 +0400	[thread overview]
Message-ID: <CAOp4FwTbmaNB4P8XLSfK1nTYOHSiAkfBaG4w9c2qXbcE1FznKg@mail.gmail.com> (raw)
In-Reply-To: <trinity-2dcb8602-8fe9-4606-9e91-0c8b38ecba71-1474231843525@3capp-gmx-bs05>

On Mon, Sep 19, 2016 at 12:50 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Loganaden,
>
> this sounds somewhat familiar to me (see
> https://bugs.lede-project.org/index.php?do=details&task_id=176 ). At least
> the symptoms are similar and so is the temporary remedy (calling wifi on the
> CLI). Are you using LEDE firmwares as well? In my case it seems bad radio
> conditions help expose the issue somewhat easier... My current idea is that
> r1482 (commit    372d0fea29e60b02154fd7176ba32e7742f6640e, ' ath9k: add a
> bunch of powersave handling fixes') somehow introduced a new or exposed an
> old and hidden bug for the atheros radios, r1483 (commit
> a894a535ff7e6c37bd853e951663130482bc0ff2, 'mac80211: add fixes for dealing
> with unexpected BlockAck frames') might either have introduced an easier way
> to trigger the offensive conditions, but that is conjecture...
>

I'm using this firmware:

https://kau.toke.dk/lede/airtime-fairness-builds/ar71xx/generic/lede-r1526%2B2-ar71xx-generic-archer-c7-v2-squashfs-factory.bin

  reply	other threads:[~2016-09-19  3:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 21:42 Dave Taht
2016-09-17  8:33 ` Loganaden Velvindron
2016-09-17 17:12 ` Loganaden Velvindron
2016-09-17 17:26   ` Loganaden Velvindron
2016-09-17 17:33     ` Dave Taht
2016-09-17 17:35     ` Toke Høiland-Jørgensen
2016-09-17 17:50       ` Loganaden Velvindron
2016-09-18  5:39         ` Loganaden Velvindron
2016-09-18  6:19           ` Dave Taht
2016-09-18  6:27             ` Loganaden Velvindron
2016-09-18 14:24               ` Loganaden Velvindron
2016-09-18 20:50                 ` Sebastian Moeller
2016-09-19  3:56                   ` Loganaden Velvindron [this message]
2016-09-19  8:33                     ` moeller0
2016-09-19 11:27                       ` Toke Høiland-Jørgensen
2016-09-19 11:36                         ` moeller0

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/make-wifi-fast.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAOp4FwTbmaNB4P8XLSfK1nTYOHSiAkfBaG4w9c2qXbcE1FznKg@mail.gmail.com \
    --to=loganaden@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --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