Message-ID: <5138A4C8.7040500@neratec.com> (sfid-20130307_153726_629804_0BA8646D)
Date: Thu, 07 Mar 2013 15:31:36 +0100
From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
MIME-Version: 1.0
To: Felix Fietkau <nbd@openwrt.org>
CC: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	mcgrof@qca.qualcomm.com, stable@vger.kernel.org
Subject: Re: [PATCH 3.8 1/3] ath9k_hw: fix calibration issues on chainmask
 that don't include chain 0
References: <1358715322-46447-1-git-send-email-nbd@openwrt.org>
In-Reply-To: <1358715322-46447-1-git-send-email-nbd@openwrt.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Sender: linux-wireless-owner@vger.kernel.org

There is a regression introduced by this patch when power save is off on
the station for idle checks.
I have AR9590 station with rx and tx chain set to 0x1 connected
to legacy AP (based on Ar9390) with RF cable and 40dB attenuator.

Before this patch in connection polling the station was properly sending
null function to check whether AP is still there. After this patch it sends
broadcast probe request which is anyway wrong or some 16 or so packets
of random data (rarely). It manifests itself in lost connection because 
there
is no ack from AP which is expected for null function.

I have been following skb's up to the descriptor setting in ath9k and it was
all ok i.e. proper null function with valid addresses.

I have been bisecting it twice because it doesn't make much sense but maybe
it's a HW issue?


Wojtek