RE: ath10k firmware crashes in mesh mode on QCA9880

2016-12-05 Thread Nagarajan, Ashok Raj
>> Applied the patch and tried with 10.2.4.70.54 firmware and it still crashes:

>> [  142.438377] ath10k_pci :01:00.0: firmware crashed! (uuid 
>> a5499582-e220-46d2-9359-0b44219f69ea)
>> [  142.447512] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c 
>> chip_id 0x043202ff sub :
>> [  142.456879] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 
>> tracing 0 dfs 1 testmode 1
>> [  142.469916] ath10k_pci :01:00.0: firmware ver 10.2.4.70.54 api 5 
features no-p2p,raw-mode,mfp crc32 9d340dd9
>> [  142.480295] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A 
>> crc32 bebc7c08
>> [  142.487717] ath10k_pci :01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 
>> cal file max-sta 128 raw 0 hwcrypto 1
>> [  142.499361] ath10k_pci :01:00.0: firmware register dump:
>> [  142.505124] ath10k_pci :01:00.0: [00]: 0x4100016C 0x15B3 
0x009A4577 0x00955B31

Benjamin, Thanks for the logs.
Quick questions to further debug the issue here,

1. Is this issue seen every time you start sending data traffic?
2. Issue seen with older firmwares? (FYR, 
http://linuxwireless.org/en/users/Drivers/ath10k/firmware/ )
3. Could you please share the dmesg from your device after enabling MAC and WMI 
logs in ath10k driver
To enable debug logs please see 
http://linuxwireless.org/en/users/Drivers/ath10k/debug/ 
4. Do you know what is the Number of Spatial Streams seen in mesh beacons and 
in mesh data packet?

Thanks,
Ashok


Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05

2016-07-15 Thread Nagarajan, Ashok Raj
> On 06/10/2016 05:57 AM, Felix Fietkau wrote:
>>> On 2016-06-10 14:52, Ben Greear wrote:
>>> This looks a lot like the problems I was having.
>>>
>>> Two of these 5 patches recently made it upstream (but may not be in LEDE 
>>> yet),
>>> but the other patches also were related to memory corruption.
>>>
>>> See my patches posted on 4/1/16:
>>>
>>> https://patchwork.kernel.org/project/ath10k/list/
>>>
>>> I don't know where the 5/5 patch ended up.
>> I had already asked affected users to test with those patches (I have a
>> commit that adds them in my staging tree), but it did not resolve the issue.
>
>Ok, must be something else then.
>
>If you can run on x86 under KASAN it may provide some clues..that is how I 
>eventually
>made progress on the issues I was seeing.  My rebase onto 3.7 has been slow 
>and painful,
>but I should be ready to start testing that sometime soon, maybe I can 
>reproduce something
>there.

Hi Benz,

Could you please check with the following diff if it is solving your issue?

diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c 
b/drivers/net/wireless/ath/ath10k/htt_rx.c
index 6f19fca..c192a41 100644
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -1528,7 +1528,7 @@ static void ath10k_htt_rx_h_filter(struct ath10k *ar,
static int ath10k_htt_rx_handle_amsdu(struct ath10k_htt *htt)
{
struct ath10k *ar = htt->ar;
-   static struct ieee80211_rx_status rx_status;
+   struct ieee80211_rx_status *rx_status = &htt->rx_status;
struct sk_buff_head amsdu;
int ret;
 
@@ -1553,11 +1553,11 @@ static int ath10k_htt_rx_handle_amsdu(struct ath10k_htt 
*htt)
}
 
ath10k_pktlog_rx(ar, &amsdu);
-   ath10k_htt_rx_h_ppdu(ar, &amsdu, &rx_status, 0x);
+   ath10k_htt_rx_h_ppdu(ar, &amsdu, rx_status, 0x);
ath10k_htt_rx_h_unchain(ar, &amsdu, ret > 0);
-   ath10k_htt_rx_h_filter(ar, &amsdu, &rx_status);
-   ath10k_htt_rx_h_mpdu(ar, &amsdu, &rx_status);
-   ath10k_htt_rx_h_deliver(ar, &amsdu, &rx_status);
+   ath10k_htt_rx_h_filter(ar, &amsdu, rx_status);
+   ath10k_htt_rx_h_mpdu(ar, &amsdu, rx_status);
+   ath10k_htt_rx_h_deliver(ar, &amsdu, rx_status);

Thanks,
Ashok

>Thanks,
>Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH] cfg80211: add debugfs VHT80 allow map

2015-02-08 Thread Nagarajan, Ashok Raj
Hi Johannes,

I see your point here. I will upload one patch for printing this info from iw.

I will also write another patch for removing HT40 one?

Thanks,
Ashok

From: Johannes Berg 
Sent: Saturday, February 7, 2015 12:41 AM
To: Nagarajan, Ashok Raj
Cc: linux-wireless@vger.kernel.org; Manoharan, Rajkumar; Thiagarajan, 
Vasanthakumar
Subject: Re: [PATCH] cfg80211: add debugfs VHT80 allow map

On Fri, 2015-02-06 at 12:05 +0530, Ashok Raj Nagarajan wrote:
> Here is a output of this debugfs entry
>
> root@OpenWrt:/# cat /sys/kernel/debug/ieee80211/phy0/vht80allow_map
> 2412 VHT80 N

I'm not sure I see much point in this, in fact we could remove the HT40
one?

We expose this data to userspace, so you could change 'iw' to print it
when dumping the list of channels in 'iw list' or similar.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html