From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 13:14:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A86E3778; Sun, 10 Nov 2013 13:14:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 578262A0B; Sun, 10 Nov 2013 13:14:59 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id k4so1039342qaq.5 for ; Sun, 10 Nov 2013 05:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=gCzs9enMzqjBI5+D5hUYgbc9khaveCJbJbx+1nMUnik=; b=jPZZaKV9IaWFsMJBHZZRafpmGuLuc0ui6la3Evy7R5FQB+vefR5GcKzt90SwnE69z6 DO0TbUgv+VkF73w6YTC+79FxqARCr2qTUiPEKxdO7HT5Q3NUiZbGDvg51BzLz8he4cfw +oRkpXgdnjZfb+BljM+Fl59zVO1pUMnO70/Dyh78M2I6H+5G5LXe3uNC3QkQqodsCtpw MgCfS0vzgol6MSzEDz1KA9df2oJOYEPoNUeBWP9Ii04Y6xC4iy32uG3dQyyfPjqSmaJ+ +agEgRDedjcoJU+Ccd8pHXp4rLtnbuO5EcWFzNISxIbxs5WhbzqKLFSfTCkmjMgc6P7a 3lbQ== MIME-Version: 1.0 X-Received: by 10.49.71.207 with SMTP id x15mr38649485qeu.49.1384089298426; Sun, 10 Nov 2013 05:14:58 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 10 Nov 2013 05:14:58 -0800 (PST) In-Reply-To: <20131110121737.GA1834@mole.fafoe.narf.at> References: <20131110121737.GA1834@mole.fafoe.narf.at> Date: Sun, 10 Nov 2013 05:14:58 -0800 X-Google-Sender-Auth: _ywop-ht8jkO9gzE9z6sNLC-7q0 Message-ID: Subject: Re: iwn(4) hangs after r257133 From: Adrian Chadd To: Stefan Farfeleder Content-Type: text/plain; charset=ISO-8859-1 Cc: Brandon Gooch , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 13:14:59 -0000 yup, same info as brandon. :) -a On 10 November 2013 04:17, Stefan Farfeleder 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