Hi Daniel,
On Fri, Nov 4, 2011 at 12:58 AM, Daniel Smith <[email protected]> wrote:
> I recently upgraded to compat-wireless-3.1-rc8 from
> compat-wireless-2.6.39-1-sn and have discovered an interesting behavior.
> When in monitor mode I use the signal strength field reported in
> radiotap and with 3.1 I am now getting a range of values. The more
> interesting ones are all the frames reporting a signal of 110+ dBm. To
> see what is being pulled from the descriptors I dumped rs->rs_rssi to
> klog when the value was larger than 95. Below is a snippet showing the
> ranging values,
i tried with the AR9382 card in 3.1.0-wl with the attached debug
patch, can you please give a sample log with the patch applied and
putting the interface in monitor mode. did you print/check rs_rssi
somewhere else?
did you also try with the latest package
http://linuxwireless.org/download/compat-wireless-2.6/
>
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.907908] [ath9k]: RSSI 107
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.911697] [ath9k]: RSSI -61
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913553] [ath9k]: RSSI -119
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913562] [ath9k]: RSSI -59
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.913570] [ath9k]: RSSI -94
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915880] [ath9k]: RSSI 119
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915890] [ath9k]: RSSI -109
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.915898] [ath9k]: RSSI 123
> Nov 3 15:00:03 dpsmith-dev-system kernel: [ 5319.917743] [ath9k]: RSSI 101
>
> A couple of data points,
> 1. I have tested two different cards, one having AR9106+AR9160 and one
> with an AR9382.
>
> 2. It appears that it is always the same devices that this occurs for,
> e.g. pretty confident there are some devices that I collected that I did
> not see anything out of the 3-10dBm range
>
> I know 2.6.39 -> 3.1 is a bit of a jump, but I wanted to push this to
> the community to see if there are some thoughts or opinions while I dig
> deeper. My next step is to see if it occurs in 3.0 which should help
> give me a narrow set of patches to review/bisect to see at what point
> this was introduced. I would suspect it to be an initval issue, but the
> two chips I have should have different initval sets. Any thoughts or
> suggestions would be greatly appreciated.
>
> dps
>
> _______________________________________________
> ath9k-devel mailing list
> [email protected]
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
shafi
diff --git a/drivers/net/wireless/ath/ath9k/recv.c b/drivers/net/wireless/ath/ath9k/recv.c
index 67b862c..378f202 100644
--- a/drivers/net/wireless/ath/ath9k/recv.c
+++ b/drivers/net/wireless/ath/ath9k/recv.c
@@ -1003,6 +1003,7 @@ static int ath9k_rx_skb_preprocess(struct ath_common *common,
rx_status->band = hw->conf.channel->band;
rx_status->freq = hw->conf.channel->center_freq;
rx_status->signal = ah->noise + rx_stats->rs_rssi;
+ printk("\nnoise = %d, rs_rssi = %d, signal =%d", ah->noise, rx_stats->rs_rssi, rx_status->signal);
rx_status->antenna = rx_stats->rs_antenna;
rx_status->flag |= RX_FLAG_MACTIME_MPDU;
_______________________________________________
ath9k-devel mailing list
[email protected]
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
