From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 12:17:53 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 C2D8BE1F; Sun, 10 Nov 2013 12:17:53 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep14.mx.upcmail.net (fep14.mx.upcmail.net [62.179.121.34]) by mx1.freebsd.org (Postfix) with ESMTP id DA3F8270A; Sun, 10 Nov 2013 12:17:52 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep14-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131110121751.EXU23106.viefep14-int.chello.at@edge01.upcmail.net>; Sun, 10 Nov 2013 13:17:51 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge01.upcmail.net with edge id noHe1m00Y2xdvHc01oHekh; Sun, 10 Nov 2013 13:17:40 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id 271AB6D44C; Sun, 10 Nov 2013 13:17:38 +0100 (CET) Date: Sun, 10 Nov 2013 13:17:38 +0100 From: Stefan Farfeleder To: Brandon Gooch Subject: Re: iwn(4) hangs after r257133 Message-ID: <20131110121737.GA1834@mole.fafoe.narf.at> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Adrian Chadd , 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 12:17:53 -0000 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