* Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
@ 2014-03-04 6:33 Yeoh Chun-Yeow
2014-03-04 7:23 ` Michal Kazior
0 siblings, 1 reply; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-04 6:33 UTC (permalink / raw)
To: ath10k
Hi, all
I have observed that only minimum legacy rate 6Mbps used by two nodes
setting up in adhoc mode.
Currently, there is no implementation on
IEEE80211_RC_SUPP_RATES_CHANGED. So I just disassociate, delete,
create and associate node back in HT mode as printed below, but no
luck the TxRate is stuck at 6Mbps
[ 339.550000] ath10k: mac vdev 0 peer create 04:f0:21:0c:a5:1c (new
sta) num_peers 2
[ 339.550000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:1c
[ 339.550000] ath10k: mac sta 04:f0:21:0c:a5:1c associated
[ 339.550000] ath10k: mac peer 04:f0:21:0c:a5:1c phymode 11a
[ 339.550000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:1c
[ 339.550000] ath10k: mac sta rc update for 04:f0:21:0c:a5:1c changed
00000004 bw 0 nss 1 smps 2
[ 339.550000] ath10k: mac sta rc update for 04:f0:21:0c:a5:1c:
changing supported rates not implemented
[ 339.550000] ath10k: wmi peer delete vdev_id 0 peer_addr 04:f0:21:0c:a5:1c
[ 339.550000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:1c
[ 339.550000] ath10k: mac ht peer 04:f0:21:0c:a5:1c mcs cnt 24 nss 1
[ 339.550000] ath10k: mac peer 04:f0:21:0c:a5:1c phymode 11na-ht20
[ 339.550000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:1c
[ 339.550000] ath10k: wmi vdev 0 peer 0x04:f0:21:0c:a5:1c set param 1 value 1
[ 339.850000] ath10k: wmi event debug mesg len 84
Try to re-associate by simply tweaking the peer_new_assoc bit also the same.
Anyone has any ideas?
-----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 6:33 Only Lowest Legacy Rate 6Mbps used by Adhoc Mode Yeoh Chun-Yeow
@ 2014-03-04 7:23 ` Michal Kazior
2014-03-04 7:29 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 11+ messages in thread
From: Michal Kazior @ 2014-03-04 7:23 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: ath10k
On 4 March 2014 07:33, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Hi, all
>
> I have observed that only minimum legacy rate 6Mbps used by two nodes
> setting up in adhoc mode.
>
> Currently, there is no implementation on
> IEEE80211_RC_SUPP_RATES_CHANGED. So I just disassociate, delete,
> create and associate node back in HT mode as printed below, but no
> luck the TxRate is stuck at 6Mbps
If you refer to what driver reports (via nl80211 to userspace) then
this is expected. Current FW/HW isn't capable of reporting tx rate for
each sent frame so ath10k always reports 6mbps.
Or do you refer to what you see on a sniffer?
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 7:23 ` Michal Kazior
@ 2014-03-04 7:29 ` Yeoh Chun-Yeow
2014-03-04 8:46 ` Janusz Dziedzic
0 siblings, 1 reply; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-04 7:29 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
> If you refer to what driver reports (via nl80211 to userspace) then
> this is expected. Current FW/HW isn't capable of reporting tx rate for
> each sent frame so ath10k always reports 6mbps.
>
> Or do you refer to what you see on a sniffer?
>
Nope. This is the rate captured by wireshark and also confirm with the
following:
[ 3807.810000] ath10k: rx skb 86c77480 len 116 rate_idx 0 vht_nss 0
freq 5180 band 1 flag 0x200000 fcs-err 0
[ 3808.810000] ath10k: rx skb 8735fc00 len 116 rate_idx 0 vht_nss 0
freq 5180 band 1 flag 0x200000 fcs-err 0
[ 3809.810000] ath10k: rx skb 8738b9c0 len 116 rate_idx 0 vht_nss 0
freq 5180 band 1 flag 0x200000 fcs-err 0
It seems that it always stuck at 6Mbps legacy rate. Any idea why?
-----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 7:29 ` Yeoh Chun-Yeow
@ 2014-03-04 8:46 ` Janusz Dziedzic
2014-03-04 9:18 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 11+ messages in thread
From: Janusz Dziedzic @ 2014-03-04 8:46 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Michal Kazior, ath10k
On 4 March 2014 08:29, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> If you refer to what driver reports (via nl80211 to userspace) then
>> this is expected. Current FW/HW isn't capable of reporting tx rate for
>> each sent frame so ath10k always reports 6mbps.
>>
>> Or do you refer to what you see on a sniffer?
>>
>
> Nope. This is the rate captured by wireshark and also confirm with the
> following:
>
> [ 3807.810000] ath10k: rx skb 86c77480 len 116 rate_idx 0 vht_nss 0
> freq 5180 band 1 flag 0x200000 fcs-err 0
> [ 3808.810000] ath10k: rx skb 8735fc00 len 116 rate_idx 0 vht_nss 0
> freq 5180 band 1 flag 0x200000 fcs-err 0
> [ 3809.810000] ath10k: rx skb 8738b9c0 len 116 rate_idx 0 vht_nss 0
> freq 5180 band 1 flag 0x200000 fcs-err 0
>
> It seems that it always stuck at 6Mbps legacy rate. Any idea why?
>
You can try to set/force tx rate using iw:
Eg. setup legacy 18Mbps
iw wlanX set bitrates legacy-5 18 ht-mcs-5 vht-mcs-5
Set nss=1
iw wlanX set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:0-9
And check using sniffer if that will work - I didn't check adhoc.
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 8:46 ` Janusz Dziedzic
@ 2014-03-04 9:18 ` Yeoh Chun-Yeow
2014-03-04 9:31 ` Michal Kazior
0 siblings, 1 reply; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-04 9:18 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: Michal Kazior, ath10k
> You can try to set/force tx rate using iw:
>
> Eg. setup legacy 18Mbps
> iw wlanX set bitrates legacy-5 18 ht-mcs-5 vht-mcs-5
>
> Set nss=1
> iw wlanX set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:0-9
>
> And check using sniffer if that will work - I didn't check adhoc.
>
Yes, this work. I can even force the HT rate.
[ 559.410000] ath10k: rx skb 86feec00 len 116 ht rate_idx 7 vht_nss 0
freq 5180 band 1 flag 0x200200 fcs-err 0
[ 560.410000] ath10k: rx skb 86884900 len 116 ht rate_idx 7 vht_nss 0
freq 5180 band 1 flag 0x200200 fcs-err 0
Hmm, it seems that rate control is not working for adhoc. Where to
look for a fix?
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 9:18 ` Yeoh Chun-Yeow
@ 2014-03-04 9:31 ` Michal Kazior
2014-03-04 9:51 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 11+ messages in thread
From: Michal Kazior @ 2014-03-04 9:31 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Janusz Dziedzic, ath10k
On 4 March 2014 10:18, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> You can try to set/force tx rate using iw:
>>
>> Eg. setup legacy 18Mbps
>> iw wlanX set bitrates legacy-5 18 ht-mcs-5 vht-mcs-5
>>
>> Set nss=1
>> iw wlanX set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:0-9
>>
>> And check using sniffer if that will work - I didn't check adhoc.
>>
>
> Yes, this work. I can even force the HT rate.
> [ 559.410000] ath10k: rx skb 86feec00 len 116 ht rate_idx 7 vht_nss 0
> freq 5180 band 1 flag 0x200200 fcs-err 0
> [ 560.410000] ath10k: rx skb 86884900 len 116 ht rate_idx 7 vht_nss 0
> freq 5180 band 1 flag 0x200200 fcs-err 0
>
> Hmm, it seems that rate control is not working for adhoc. Where to
> look for a fix?
Hmm.. if I assume ath10k_sta_state() isn't called for AUTH->ASSOC
(which probably isn't unreasonable to consider since IBSS doesn't have
an association sequence, does it?) then ath10k_station_assoc() isn't
called and neither is ath10k_wmi_peer_assoc() which I suspect setups
HW rate control.
Can you check if the ath10k_wmi_peer_assoc() is called or not and what
are the station state transitions (I think mac80211 traces provide the
transition debug)?
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 9:31 ` Michal Kazior
@ 2014-03-04 9:51 ` Yeoh Chun-Yeow
2014-03-04 9:56 ` Michal Kazior
0 siblings, 1 reply; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-04 9:51 UTC (permalink / raw)
To: Michal Kazior; +Cc: Janusz Dziedzic, ath10k
> Hmm.. if I assume ath10k_sta_state() isn't called for AUTH->ASSOC
> (which probably isn't unreasonable to consider since IBSS doesn't have
> an association sequence, does it?) then ath10k_station_assoc() isn't
> called and neither is ath10k_wmi_peer_assoc() which I suspect setups
> HW rate control.
Nope, the mac80211 will move the STA state to AUTH and ASSOC when the
STA is added but as legacy STA. So ath10k_station_assoc is called as
shown below:
[ 445.080000] ath10k: mac vdev 0 peer create 04:f0:21:0c:a5:44 (new
sta) num_peers 2
[ 445.080000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:44
[ 445.080000] ath10k: mac sta 04:f0:21:0c:a5:44 associated
[ 445.080000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11a
--------> [first association with legacy]
[ 445.080000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
[ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44 changed
00000004 bw 0 nss 1 smps 2
[ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44:
changing supported rates not implemented [upgrade the rate]
[ 445.170000] ath10k: wmi peer delete vdev_id 0 peer_addr
04:f0:21:0c:a5:44 -----------> [delete peer]
[ 445.170000] ath10k: wmi peer create vdev_id 0 peer_addr
04:f0:21:0c:a5:44 -----------> [create peer]
[ 445.170000] ath10k: mac ht peer 04:f0:21:0c:a5:44 mcs cnt 24 nss 1
[ 445.170000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11na-ht20
[ 445.170000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
------------> [associate peer again with HT]
[ 445.170000] ath10k: wmi vdev 0 peer 0x04:f0:21:0c:a5:44 set param 1 value 1
My further investigation shows that the rate control is working when
you added and associated the STA at first.
Later on, mac80211 found out that the adhoc node can support HT or VHT
and try to call drv_sta_rc_update. But since the
IEEE80211_RC_SUPP_RATES_CHANGED is not implemented, I try to add the
code to disassoc -> delete -> create -> assoc the STA again. But the
rate control is no longer working (but you can fix the HT rate as
suggested by Janusz Dziedzic). So what went wrong?
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 9:51 ` Yeoh Chun-Yeow
@ 2014-03-04 9:56 ` Michal Kazior
2014-03-04 10:36 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 11+ messages in thread
From: Michal Kazior @ 2014-03-04 9:56 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Janusz Dziedzic, ath10k
On 4 March 2014 10:51, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> Hmm.. if I assume ath10k_sta_state() isn't called for AUTH->ASSOC
>> (which probably isn't unreasonable to consider since IBSS doesn't have
>> an association sequence, does it?) then ath10k_station_assoc() isn't
>> called and neither is ath10k_wmi_peer_assoc() which I suspect setups
>> HW rate control.
>
> Nope, the mac80211 will move the STA state to AUTH and ASSOC when the
> STA is added but as legacy STA. So ath10k_station_assoc is called as
> shown below:
>
> [ 445.080000] ath10k: mac vdev 0 peer create 04:f0:21:0c:a5:44 (new
> sta) num_peers 2
> [ 445.080000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:44
> [ 445.080000] ath10k: mac sta 04:f0:21:0c:a5:44 associated
> [ 445.080000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11a
> --------> [first association with legacy]
> [ 445.080000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
> [ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44 changed
> 00000004 bw 0 nss 1 smps 2
> [ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44:
> changing supported rates not implemented [upgrade the rate]
> [ 445.170000] ath10k: wmi peer delete vdev_id 0 peer_addr
> 04:f0:21:0c:a5:44 -----------> [delete peer]
> [ 445.170000] ath10k: wmi peer create vdev_id 0 peer_addr
> 04:f0:21:0c:a5:44 -----------> [create peer]
> [ 445.170000] ath10k: mac ht peer 04:f0:21:0c:a5:44 mcs cnt 24 nss 1
> [ 445.170000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11na-ht20
> [ 445.170000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
> ------------> [associate peer again with HT]
> [ 445.170000] ath10k: wmi vdev 0 peer 0x04:f0:21:0c:a5:44 set param 1 value 1
>
> My further investigation shows that the rate control is working when
> you added and associated the STA at first.
>
> Later on, mac80211 found out that the adhoc node can support HT or VHT
> and try to call drv_sta_rc_update. But since the
> IEEE80211_RC_SUPP_RATES_CHANGED is not implemented, I try to add the
> code to disassoc -> delete -> create -> assoc the STA again. But the
> rate control is no longer working (but you can fix the HT rate as
> suggested by Janusz Dziedzic). So what went wrong?
Perhaps FW doesn't support HT with IBSS at all?
Can you get peer assoc command dump (after normal assoc and after rc
update), please? I'm curious what actually gets sent to firmware.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 9:56 ` Michal Kazior
@ 2014-03-04 10:36 ` Yeoh Chun-Yeow
2014-03-04 10:52 ` Michal Kazior
0 siblings, 1 reply; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-04 10:36 UTC (permalink / raw)
To: Michal Kazior; +Cc: Janusz Dziedzic, ath10k
[-- Attachment #1: Type: text/plain, Size: 2724 bytes --]
Attached is the dump file of the command. Let me know whether this is
sufficient.
-----
Chun-Yeow
On Tue, Mar 4, 2014 at 5:56 PM, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 4 March 2014 10:51, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>>> Hmm.. if I assume ath10k_sta_state() isn't called for AUTH->ASSOC
>>> (which probably isn't unreasonable to consider since IBSS doesn't have
>>> an association sequence, does it?) then ath10k_station_assoc() isn't
>>> called and neither is ath10k_wmi_peer_assoc() which I suspect setups
>>> HW rate control.
>>
>> Nope, the mac80211 will move the STA state to AUTH and ASSOC when the
>> STA is added but as legacy STA. So ath10k_station_assoc is called as
>> shown below:
>>
>> [ 445.080000] ath10k: mac vdev 0 peer create 04:f0:21:0c:a5:44 (new
>> sta) num_peers 2
>> [ 445.080000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:44
>> [ 445.080000] ath10k: mac sta 04:f0:21:0c:a5:44 associated
>> [ 445.080000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11a
>> --------> [first association with legacy]
>> [ 445.080000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
>> [ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44 changed
>> 00000004 bw 0 nss 1 smps 2
>> [ 445.160000] ath10k: mac sta rc update for 04:f0:21:0c:a5:44:
>> changing supported rates not implemented [upgrade the rate]
>> [ 445.170000] ath10k: wmi peer delete vdev_id 0 peer_addr
>> 04:f0:21:0c:a5:44 -----------> [delete peer]
>> [ 445.170000] ath10k: wmi peer create vdev_id 0 peer_addr
>> 04:f0:21:0c:a5:44 -----------> [create peer]
>> [ 445.170000] ath10k: mac ht peer 04:f0:21:0c:a5:44 mcs cnt 24 nss 1
>> [ 445.170000] ath10k: mac peer 04:f0:21:0c:a5:44 phymode 11na-ht20
>> [ 445.170000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
>> ------------> [associate peer again with HT]
>> [ 445.170000] ath10k: wmi vdev 0 peer 0x04:f0:21:0c:a5:44 set param 1 value 1
>>
>> My further investigation shows that the rate control is working when
>> you added and associated the STA at first.
>>
>> Later on, mac80211 found out that the adhoc node can support HT or VHT
>> and try to call drv_sta_rc_update. But since the
>> IEEE80211_RC_SUPP_RATES_CHANGED is not implemented, I try to add the
>> code to disassoc -> delete -> create -> assoc the STA again. But the
>> rate control is no longer working (but you can fix the HT rate as
>> suggested by Janusz Dziedzic). So what went wrong?
>
> Perhaps FW doesn't support HT with IBSS at all?
>
> Can you get peer assoc command dump (after normal assoc and after rc
> update), please? I'm curious what actually gets sent to firmware.
>
>
> Michał
[-- Attachment #2: dump_adhoc --]
[-- Type: application/octet-stream, Size: 6484 bytes --]
[ 72.110000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:44
[ 72.110000] ath10k: pci tx item 0 paddr 0x071d5e30 len 24 n_items 1
[ 72.110000] item data: 00000000: 02 01 10 00 00 a1 00 00 01 60 00 00 00 00 00 00 .........`......
[ 72.110000] item data: 00000010: 04 f0 21 0c a5 44 00 00 ..!..D..
[ 72.110000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
[ 72.110000] ath10k: pci tx item 0 paddr 0x07398830 len 368 n_items 1
[ 72.110000] item data: 00000000: 02 00 68 01 08 a2 00 00 05 60 00 00 04 f0 21 0c ..h......`....!.
[ 72.110000] item data: 00000010: a5 44 00 00 00 00 00 00 01 00 00 00 00 00 00 00 .D..............
[ 72.110000] item data: 00000020: 01 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 ................
[ 72.110000] item data: 00000040: 0c 12 18 24 30 48 60 6c 00 00 00 00 00 00 00 00 ...$0H`l........
[ 72.110000] item data: 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 000000f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000140: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 ................
[ 72.110000] item data: 00000150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] item data: 00000160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.110000] ath10k: Disassociate, delete, create and associate again
[ 72.120000] ath10k: wmi peer delete vdev_id 0 peer_addr 04:f0:21:0c:a5:44
[ 72.120000] ath10k: pci tx item 0 paddr 0x071d5230 len 24 n_items 1
[ 72.120000] item data: 00000000: 02 01 10 00 20 a3 30 30 02 60 00 00 00 00 00 00 .... .00.`......
[ 72.120000] item data: 00000010: 04 f0 21 0c a5 44 00 00 ..!..D..
[ 72.130000] ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0c:a5:44
[ 72.130000] ath10k: pci tx item 0 paddr 0x07259230 len 24 n_items 1
[ 72.130000] item data: 00000000: 02 01 10 00 20 a5 30 30 01 60 00 00 00 00 00 00 .... .00.`......
[ 72.130000] item data: 00000010: 04 f0 21 0c a5 44 00 00 ..!..D..
[ 72.130000] ath10k: wmi peer assoc vdev 0 addr 04:f0:21:0c:a5:44
[ 72.130000] ath10k: pci tx item 0 paddr 0x0739c830 len 368 n_items 1
[ 72.130000] item data: 00000000: 02 00 68 01 00 a6 00 00 05 60 00 00 04 f0 21 0c ..h......`....!.
[ 72.130000] item data: 00000010: a5 44 00 00 00 00 00 00 01 00 00 00 00 00 00 00 .D..............
[ 72.130000] item data: 00000020: 01 90 01 00 00 00 00 00 05 00 00 00 e3 19 00 00 ................
[ 72.130000] item data: 00000030: ff ff 00 00 08 00 00 00 6c 02 00 00 08 00 00 00 ........l.......
[ 72.130000] item data: 00000040: 0c 12 18 24 30 48 60 6c 00 00 00 00 00 00 00 00 ...$0H`l........
[ 72.130000] item data: 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 000000a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 000000b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 000000c0: 00 00 00 00 18 00 00 00 00 01 02 03 04 05 06 07 ................
[ 72.130000] item data: 000000d0: 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 ................
[ 72.130000] item data: 000000e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 000000f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000140: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 ................
[ 72.130000] item data: 00000150: 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] item data: 00000160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 72.130000] ath10k: wmi vdev 0 peer 0x04:f0:21:0c:a5:44 set param 1 value 1
[ 72.130000] ath10k: pci tx item 0 paddr 0x07259030 len 32 n_items 1
[ 72.130000] item data: 00000000: 02 01 18 00 00 a7 00 00 04 60 00 00 00 00 00 00 .........`......
[ 72.130000] item data: 00000010: 04 f0 21 0c a5 44 00 00 01 00 00 00 01 00 00 00 ..!..D..........
[ 72.470000] ath10k: wmi event debug mesg len 84
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 10:36 ` Yeoh Chun-Yeow
@ 2014-03-04 10:52 ` Michal Kazior
2014-03-05 4:30 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 11+ messages in thread
From: Michal Kazior @ 2014-03-04 10:52 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Janusz Dziedzic, ath10k
On 4 March 2014 11:36, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Attached is the dump file of the command. Let me know whether this is
> sufficient.
Thank you.
I don't see anything suspicious in the logs :-(
Let me get one thing clear -- calling to sta_rc_update *without* your
supp_rates implementation doesn't yield 6mbps tx rate drop?
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Only Lowest Legacy Rate 6Mbps used by Adhoc Mode
2014-03-04 10:52 ` Michal Kazior
@ 2014-03-05 4:30 ` Yeoh Chun-Yeow
0 siblings, 0 replies; 11+ messages in thread
From: Yeoh Chun-Yeow @ 2014-03-05 4:30 UTC (permalink / raw)
To: Michal Kazior; +Cc: Janusz Dziedzic, ath10k
> Let me get one thing clear -- calling to sta_rc_update *without* your
> supp_rates implementation doesn't yield 6mbps tx rate drop?
Yes.
I investigate the issue a bit further by modifying the ibss.c and also mac.c
Case 1:
Create, Associate (Legacy Rate), Disassociate, Delete, Create,
Associate (HT Rate)
--- TxRate always stuck at 6Mbps
Case 2:
Create, Associate (Legacy Rate), Disassociate, Delete, Create,
Associate (Legacy Rate)
--- Rate control works with TxRate going out to 54Mbps even after
delete and associate back the STA.
Case 3:
Create, Associate (HT Rate)
--- TxRate always stuck at 6Mbps
So it seems that the rate control is not working in the FW whenever
you configure the HT mode for the adhoc mode.
Any idea how to solve this?
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2014-03-05 4:30 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-04 6:33 Only Lowest Legacy Rate 6Mbps used by Adhoc Mode Yeoh Chun-Yeow
2014-03-04 7:23 ` Michal Kazior
2014-03-04 7:29 ` Yeoh Chun-Yeow
2014-03-04 8:46 ` Janusz Dziedzic
2014-03-04 9:18 ` Yeoh Chun-Yeow
2014-03-04 9:31 ` Michal Kazior
2014-03-04 9:51 ` Yeoh Chun-Yeow
2014-03-04 9:56 ` Michal Kazior
2014-03-04 10:36 ` Yeoh Chun-Yeow
2014-03-04 10:52 ` Michal Kazior
2014-03-05 4:30 ` Yeoh Chun-Yeow
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.