Date: Sun, 10 Nov 2013 13:17:38 +0100 From: Stefan Farfeleder <stefanf@FreeBSD.org> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: Adrian Chadd <adrian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: iwn(4) hangs after r257133 Message-ID: <20131110121737.GA1834@mole.fafoe.narf.at> In-Reply-To: <CALBk6yJf%2BZ_%2BF8kVPFOdQ%2B8UC3vBU3MZJGjkPfxeSkjSZ6FPbA@mail.gmail.com> References: <CALBk6yJf%2BZ_%2BF8kVPFOdQ%2B8UC3vBU3MZJGjkPfxeSkjSZ6FPbA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?20131110121737.GA1834>