Return-path: Received: from mail-qe0-f41.google.com ([209.85.128.41]:65446 "EHLO mail-qe0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751402Ab3J3D7c (ORCPT ); Tue, 29 Oct 2013 23:59:32 -0400 Received: by mail-qe0-f41.google.com with SMTP id x7so535062qeu.28 for ; Tue, 29 Oct 2013 20:59:31 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1383033823.14377.1.camel@jlt4.sipsolutions.net> References: <1382968966.17956.15.camel@jlt4.sipsolutions.net> <1383033823.14377.1.camel@jlt4.sipsolutions.net> Date: Tue, 29 Oct 2013 20:59:31 -0700 Message-ID: (sfid-20131030_045948_483580_4B996C6B) Subject: Re: iwlegacy (4965) - what would 0x8000 as the completed TX rate indicate? From: Adrian Chadd To: Johannes Berg Cc: "linux-wireless@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 29 October 2013 01:03, Johannes Berg wrote: >> Well, what's rate=0 mean? >> >> And 0x8000 is bit 11 set, which is HT40. I definitely don't have HT40 enabled. > > 0x8000 is bit 15 set, which means "antenna B", I think? Duh, sorry. was tired. :( > But then I can't seem to figure out what rate=0 means either. Should be > an OFDM rate (bit 9 not set) but 0 isn't a valid OFDM rate value. Hmm. That's why I'm confused too. I'm seeing some odd behaviour here where sometimes the NIC behaves fine, and sometimes it just gets long transmit failures on OFDM frames but is fine with CCK frames. That's why I'm digging into this. I also see the sensitivity tuning code lose the plot over time as OFDM errors are returned by the receiver and it keeps trying to compensate until it's maxed out the sensitivity tuning parameters. If I restart the NIC, it all comes back to normal for a while. Do any of these ring a bell? Thanks, -adrian