From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 02:29:31 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 0ACBCF2B; Sun, 10 Nov 2013 02:29:31 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8803205F; Sun, 10 Nov 2013 02:29:30 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id p10so3700072pdj.25 for ; Sat, 09 Nov 2013 18:29:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=ti4p346gIw0xde26TCyVdO88+MAQyRzbAM23XB2Wm+k=; b=EsRkQ9ke3fIFMP5KUkK3bNzncy1MrddJVuW289tz1iQ/lopYpRvv62K30ZIVSXgTmq WK+ZpqwDIEdMQPZ2iYsC+UUgVzRWLpvaJhQ2VrNXosbYzJU+rW5xmtiSsv/QOn8r6Wnu J2cgDgvMUOC+KiEMgHk3KAJM1rda2wIx6dDz+MZgc3x5g44u8svOTl7FOSM4ztR4fZr+ bYuXEAoZrr3yGkv+zaauejhvnU6NW1IR3RV+h92TipLzFKw98f1yDfROJbMkXMMdxvy8 NO4LdiBfN51LVUVQXT2TCGokUfLF/YIF7RGMbkggaSJhhIScZTReATdtKcHgjCBMVS8X 9wAw== MIME-Version: 1.0 X-Received: by 10.66.218.226 with SMTP id pj2mr23837196pac.62.1384050570396; Sat, 09 Nov 2013 18:29:30 -0800 (PST) Received: by 10.68.57.72 with HTTP; Sat, 9 Nov 2013 18:29:30 -0800 (PST) Date: Sat, 9 Nov 2013 20:29:30 -0600 Message-ID: Subject: iwn(4) hangs after r257133 From: Brandon Gooch To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: Adrian Chadd 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 02:29:31 -0000 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? -Brandon