Date: Sun, 10 Nov 2013 20:34:21 +0100 From: Stefan Farfeleder <stefanf@FreeBSD.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: iwn(4) hangs after r257133 Message-ID: <20131110193421.GB1778@mole.fafoe.narf.at> In-Reply-To: <CAJ-VmonxB-to30Tkq9ad830FTRpbW2=cn9nuNzXHMK67jCuNgQ@mail.gmail.com> References: <CALBk6yJf%2BZ_%2BF8kVPFOdQ%2B8UC3vBU3MZJGjkPfxeSkjSZ6FPbA@mail.gmail.com> <20131110121737.GA1834@mole.fafoe.narf.at> <CAJ-Vmom-57ZM0xsxLpL=prENzZ0j27jYNnMLk-_=HHONr3L8zA@mail.gmail.com> <20131110163340.GA1778@mole.fafoe.narf.at> <CAJ-VmonxB-to30Tkq9ad830FTRpbW2=cn9nuNzXHMK67jCuNgQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 10, 2013 at 10:48:48AM -0800, Adrian Chadd wrote: > Right near the end there you have 'status 83' which means 'transmit > failed, long retry hit' (the status codes are in if_iwnreg.h > somewhere.) The retry count hit 16, which is the max set for the > frame. > > rate=80 (hex) is MCS0. So, you're seeing retransmits and failures at > MCS0, which is a bad sign. > > But, notice how AMRR increased it to MCS2 at a couple stages, and that > _always_ fails. But AMRR waits for 10 frame transmits before it > adjusts the rate up or down. > > So yes, we do need to enable MRR again on iwn for things to behave > better. There are other issues when you start doing larger amounts of > traffic but I'll cover those later.what? > > If someone wants to take a crack at correctly implementing the link > quality table stuff again then please let me know. As I said before, > the link quality table setup code is mostly sane. The problem is > actually correctly setting 'linkq' to start at the selected rate, as > linkq is an index into that table, not the initial rate. Hi, after some trial and error I found out that disabling AMPDU makes my iwn0 usable again. Now I actually see the rate as reported by `list sta' going up and down (mostly between 54M and 121M). Before it was always fixed at 135M. Could this be related? Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131110193421.GB1778>