From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C53393B260 for ; Mon, 19 Sep 2016 07:36:14 -0400 (EDT) Received: from [172.17.3.48] ([134.76.241.253]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MMk99-1bdQgh1n1b-008Wpy; Mon, 19 Sep 2016 13:36:08 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: moeller0 In-Reply-To: <8760psgmdm.fsf@toke.dk> Date: Mon, 19 Sep 2016 13:36:07 +0200 Cc: Loganaden Velvindron , make-wifi-fast@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: <87shsyjupm.fsf@toke.dk> <8760psgmdm.fsf@toke.dk> To: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= X-Mailer: Apple Mail (2.2104) X-Provags-ID: V03:K0:7+tk6UUHwMAbrkIUwiQXcgaq8pQ/H0/T7Dq0JEn+uhvFIDXr564 wXaRVDOHgirXf+IjWGZkrRMVIo4yz8Qv4shoUuEG3XWnVXLGbNbHHO0QmkGbcpLM9c3axaV /oGQZq/gtSPv8kDMBU6Y5Ntdho2ajimTsGTOLts0SgjGuO9toHxeEsuQiz2/TwuuZcBXWV2 W7Tp3ub75jxfUAK7GBrNA== X-UI-Out-Filterresults: notjunk:1;V01:K0:th6d6qCUb/g=:O0tVEIAh1rEpVwAJExmc40 IioNimcMjUrx1ODjGZD5J5tiKnqpKKSBeoLmOcnIDgCST6LWvOZSVFr+d+NsNbPafze00LaNq od/8xzHibHc/7WBsP8XwaqcAzlmdSo9+Vlua+wb8HuV4jNZtJaI5PgmdDSl/MWg20ouSAxqb5 yXdn7X1RpVYGQwXyOdVXSzndt5ZsLkAyy51KZs7Meb1RjO+o9CDwv5aoxC5Bg9jRV+fMFYkVo 5nfDFqbCLPYngyVQKqUnlBJCYKh562ke4/3tY41rJ1bcnt7ezlP4Jk7QDoLLIjamSKZr1R0k1 VujtGzrNFlsLugUm/IUk9RTQRW2HZjkMpNKX0snm4adAk7FgVudYECxhAaD2KGcJrQHzbt4R/ AVrLlG67YTVKv7K+bGOEPlRAIbBCSF5fA9VesPdp2qoXdHJ4n7GlkWIERRawTk0QxbK7f7hp4 1Js+dP2eXke4FQpwbxByairL54b7xkNFBjJ3EE/A2cstqdV1zrzi/xV2lgsN/oiPnkdNEk8U1 +MNfs66gaHF61jF/LyEUWnkKmXz6vYN0SW96aEp21VPGLu4zFEBp/oiB0C/x3t5uQnOdBBT05 gl0ZWZorQoGvgCSIGosGGGcH9/+KGpdhxIlY7/LKPf6f2p10tnpKI/qPBAf68NIgWU+wo02rm CnIxnPP8Mi1PyvbefQ+Q7XGLf24WNVcOZTEa7DDjBslNJUzkuGFZWv6H+OPqqY+eqg/FLjQae XzB2BcIuOfm/U66tRq8eGiCe60oZHZweKaDa8WrpPzCaHzLPakt9l27fp8ZGWqdiXNQt5Y0hd q7dDz6N Subject: Re: [Make-wifi-fast] crypto-fq bug postmortem is up X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 11:36:15 -0000 Hi Toke, > On Sep 19, 2016, at 13:27 , Toke H=C3=B8iland-J=C3=B8rgensen = wrote: >=20 > moeller0 writes: >=20 >> Hi Loganaden, hi Toke, >>=20 >>> On Sep 19, 2016, at 05:56 , Loganaden Velvindron = wrote: >>>=20 >>> On Mon, Sep 19, 2016 at 12:50 AM, Sebastian Moeller = wrote: >>>>=20 >>>> Hi Loganaden, >>>>=20 >>>> this sounds somewhat familiar to me (see >>>> https://bugs.lede-project.org/index.php?do=3Ddetails&task_id=3D176 = ). 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... >>>>=20 >>>=20 >>> I'm using this firmware: >>>=20 >>> = https://kau.toke.dk/lede/airtime-fairness-builds/ar71xx/generic/lede-r1526= %2B2-ar71xx-generic-archer-c7-v2-squashfs-factory.bin >>=20 >> 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=E2=80=A6 >=20 > 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=E2=80=A6 I believe/hope I already did: = https://bugs.lede-project.org/index.php?do=3Ddetails&task_id=3D176 There = are other reports of similar failures in the tracker, but I am not fully = convinced they all have the exact same root cause. I would not be amazed = if the commits I indicated above do not introduce real bugs, but rather = expose existing issues by making the conditions to trigger the radio = loss more likely.=20 Best Regards Sebastian >=20 > -Toke