From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: moeller0 <moeller0@gmx.de>
Cc: Loganaden Velvindron <loganaden@gmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] crypto-fq bug postmortem is up
Date: Mon, 19 Sep 2016 13:27:49 +0200 [thread overview]
Message-ID: <8760psgmdm.fsf@toke.dk> (raw)
In-Reply-To: <D9DF2BAE-DD58-4FDE-9305-CA433E7BED55@gmx.de> (moeller0's message of "Mon, 19 Sep 2016 10:33:38 +0200")
moeller0 <moeller0@gmx.de> writes:
> Hi Loganaden, hi Toke,
>
>> On Sep 19, 2016, at 05:56 , Loganaden Velvindron <loganaden@gmail.com> wrote:
>>
>> 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
>
> Since this is based on LEDE r1526 it should contain the suspect
> commits 372d0fea29e60b02154fd7176ba32e7742f6640e and
> a894a535ff7e6c37bd853e951663130482bc0ff2, so this might be the exact
> same issue. I seem to be able to force this issue with moving from
> area of good reception to an area of bad reception (yeah for living in
> an old house with massive brich walls), maybe that cild work for you
> as well? I am not sure whether the issue is regarded by the LEDE
> developers as very critical yet (and rightfully so IMHO, there are
> only a few reports), so any added report might turn this more into the
> development spot light…
The patches you are talking about went in as part of debugging the
intermediate queueing implementation. Opening an issue on the LEDE bug
tracker for this might be a good idea...
-Toke
next prev parent reply other threads:[~2016-09-19 11:27 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
2016-09-19 8:33 ` moeller0
2016-09-19 11:27 ` Toke Høiland-Jørgensen [this message]
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=8760psgmdm.fsf@toke.dk \
--to=toke@toke.dk \
--cc=loganaden@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