Date: Sun, 10 Nov 2013 05:14:58 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Stefan Farfeleder <stefanf@freebsd.org> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: iwn(4) hangs after r257133 Message-ID: <CAJ-Vmom-57ZM0xsxLpL=prENzZ0j27jYNnMLk-_=HHONr3L8zA@mail.gmail.com> In-Reply-To: <20131110121737.GA1834@mole.fafoe.narf.at> References: <CALBk6yJf%2BZ_%2BF8kVPFOdQ%2B8UC3vBU3MZJGjkPfxeSkjSZ6FPbA@mail.gmail.com> <20131110121737.GA1834@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
yup, same info as brandon. :) -a On 10 November 2013 04:17, Stefan Farfeleder <stefanf@freebsd.org> wrote: > On Sat, Nov 09, 2013 at 08:29:30PM -0600, Brandon Gooch wrote: >> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link >> 5300 to hang after only a few moments of use. >> >> For now, I've just reverted only those aspects of r257133, enabling >> MRR and keeping the rate index lookup, which seems to do something on >> my hardware at least (I assume it's not the right thing based on >> Adrian's analysis, but it works never-the-less). >> >> Has anyone else hit this with Intel WiFi hardware? >> >> Also, what needs to be done to have MRR working properly? > > Hi, > > I have problems with iwn (Intel WiFi Link 5100) as well. > > Unlike my previous problems, it associates properly and works fine, at > first. But then, after some minutes, the link quality somehow > deteriorates and I see serious packet drops. Usually it gets back to > normal some minutes later, but restarting the interface "fixes" the > problem. I don't think it's a problem with the signal itself, because > other devices next to the notebook work just fine during that intervals. > > Adrian, do you have any ideas, or some data you want from me? > > Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom-57ZM0xsxLpL=prENzZ0j27jYNnMLk-_=HHONr3L8zA>