From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 19:01:17 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 C4CAA48F; Sun, 10 Nov 2013 19:01:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 744252AB7; Sun, 10 Nov 2013 19:01:17 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id k18so3419096qcv.38 for ; Sun, 10 Nov 2013 11:01:16 -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=bEuMEEA6Jrb34Hnum3HWefM0Thf05JAw7n9M7SI1nks=; b=aRHnCF1Gj/15MRnYZsmSGyIY5+XWzJYdtQ8iJXo+xeUnkz8rdPYV91fJ5YZPMs9UPw hDyTW1OxW6mq8fd9YWTyfOY2mhmfIlG/5igEXDmMVx0TQhFKabTdYTONMtDdxHZF0460 WhkjfXfQemuwR7vx896XdaVsyPQRnkDNxPuM9mnllYJlgXp7ytAVZbeNYyFtoo4BqU3w 4HsP2TYArI7Trb7iyt/CcdyRk7JKgfF9kCZfiiFdM2UYcqsyHiECi8zQpKqtHm8jUhS/ 4D0o6Z30x/NVQXjEKIpqLuAqJVoKK/5SGyfbqgzRzqrauE+iQ+uxAiGqrsKDikozyPu+ xY+g== MIME-Version: 1.0 X-Received: by 10.229.79.70 with SMTP id o6mr41153562qck.21.1384110076718; Sun, 10 Nov 2013 11:01:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 10 Nov 2013 11:01:16 -0800 (PST) In-Reply-To: References: <20131110121737.GA1834@mole.fafoe.narf.at> <20131110163340.GA1778@mole.fafoe.narf.at> Date: Sun, 10 Nov 2013 11:01:16 -0800 X-Google-Sender-Auth: ePz5vqPFH3Ekv1mtgBT4n_XfYkQ 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 19:01:17 -0000 And for reference, here's the paper: http://hal.inria.fr/docs/00/07/07/84/PDF/RR-5208.pdf -adrian On 10 November 2013 10:48, Adrian Chadd wrote: > Right near the end there you have 'status 83' which means 'transmit > failed, long retry hit' (the status codes are in if_iwnreg.h > somewhere.) The retry count hit 16, which is the max set for the > frame. > > rate=80 (hex) is MCS0. So, you're seeing retransmits and failures at > MCS0, which is a bad sign. > > But, notice how AMRR increased it to MCS2 at a couple stages, and that > _always_ fails. But AMRR waits for 10 frame transmits before it > adjusts the rate up or down. > > So yes, we do need to enable MRR again on iwn for things to behave > better. There are other issues when you start doing larger amounts of > traffic but I'll cover those later.what? > > If someone wants to take a crack at correctly implementing the link > quality table stuff again then please let me know. As I said before, > the link quality table setup code is mostly sane. The problem is > actually correctly setting 'linkq' to start at the selected rate, as > linkq is an index into that table, not the initial rate. > > Thanks! > > > > -adrian > > > On 10 November 2013 08:33, Stefan Farfeleder wrote: >> On Sun, Nov 10, 2013 at 05:14:58AM -0800, Adrian Chadd wrote: >>> yup, same info as brandon. :) >> >> http://pastebin.com/MwfL06z7 >> >> Stefan >> >>> 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 >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"