* [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
@ 2013-12-06 16:33 Tomasz Tajmajer
2013-12-06 17:25 ` Adrian Chadd
2013-12-06 17:32 ` Janusz Dziedzic
0 siblings, 2 replies; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-06 16:33 UTC (permalink / raw)
To: ath10k
Hi,
Recently, I've been making quite a lot of tests with two QWLE900V5-18
cards. I had some issues with the drivers (e.g. regarding the regulatory
domain), but I've managed to fix them on my own. However, there is one
issue that I cannot deal with.
I'm trying to get the highest throughput possible using 3x3 MIMO. The
problem is that the wifi card does not set higher rates than 2x433.3Mbps
(MCS 9, VHT-NSS 2). The specification says that it should be possible to
have 3 spatial streams.
First, I thought it is a problem with some options of hostapd, but
hostapd even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
options. Only [RX-STBC-1] may be set in the configuration (what in fact,
does not disallows the 2x433.3Mbps link, which is another issue).
Driver info shows that the driver should support 3 spatial streams.
I am not sure where is the problem, is it some bug in hostapd, which
forces the card to use 2 spatial streams only or is it the driver, which
does not enable 3 streams when it is possible. The physical connectivity
(antennas etc.) is not the problem AFAIK.
The ath10k driver used for AP is a bit hacked to always report the US
regd code
Some dumps for you:
iw version 3.13
iw phy phy0 info
Wiphy phy0
max # scan SSIDs: 16
max scan IEs length: 199 bytes
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
Band 2:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm) (no IR)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm) (no IR)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 110543 sec)
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 110543 sec)
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 110543 sec)
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 110543 sec)
* 5500 MHz [100] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{ AP } <= 7,
total <= 8, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports scan flush.
hostapd --version
hostapd v2.1-devel
dmesg (AP)
[ 4808.976236 <tel:%5B%204808.976236>] Loading modules backported from
Linux version next-20131129-0-gae5be52
[ 4808.976243 <tel:%5B%204808.976243>] Backport generated by
backports.git backports-20131129-0-g8a36e16
[ 4808.982669 <tel:%5B%204808.982669>] cfg80211: Calling CRDA to update
world regulatory domain
[ 4810.814727] ath10k_pci 0000:06:00.0: BAR 0: assigned [mem
0xf7200000-0xf73fffff 64bit]
[ 4810.819406] ath10k: MSI-X didn't succeed (1), trying MSI
[ 4810.819480] ath10k_pci 0000:06:00.0: irq 49 for MSI/MSI-X
[ 4810.819513] ath10k: MSI interrupt handling
[ 4810.861220] ath10k: Hardware name qca988x hw2.0 version 0x4100016c
[ 4811.749751] ath10k: UART prints disabled
[ 4811.756642] ath10k: firmware 10.1.389 booted
[ 4811.766282] ath10k: htt target version 2.1
[ 4811.767324] ath: EEPROM regdomain: 0x60
[ 4811.767328] ath: EEPROM indicates we should expect a direct regpair map
[ 4811.767333] ath: Country alpha2 being used: h7
[ 4811.767336] ath: Regpair used: 0x60
[ 4811.782155] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
dmesg (STA)
[110825.598266] Loading modules backported from Linux version
next-20131129-0-gae5be52
[110825.598271] Backport generated by backports.git
backports-20131129-0-g8a36e16
[110825.603361] cfg80211: Calling CRDA to update world regulatory domain
[110827.515449] ath10k_pci 0000:0c:00.0: BAR 0: assigned [mem
0xece00000-0xecffffff 64bit]
[110827.515883] ath10k: MSI-X didn't succeed (1), trying MSI
[110827.516037] ath10k_pci 0000:0c:00.0: irq 47 for MSI/MSI-X
[110827.516114] ath10k: MSI interrupt handling
[110827.561579] ath10k: Hardware name qca988x hw2.0 version 0x4100016c
[110828.778794] ath10k: UART prints disabled
[110828.785405] ath10k: firmware 999.999.0.636 booted
[110828.795890] ath10k: htt target version 2.1
[110828.797409] ath: EEPROM regdomain: 0x0
[110828.797413] ath: EEPROM indicates default country code should be used
[110828.797417] ath: doing EEPROM country->regdmn map search
[110828.797422] ath: country maps to regdmn code: 0x3a
[110828.797426] ath: Country alpha2 being
BR,
--
Tomasz Tajmajer,
Embedded Systems Engineer,
Elnovel Sp. z o.o. [Ltd.] (elnovel.com)
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-06 16:33 [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link Tomasz Tajmajer
@ 2013-12-06 17:25 ` Adrian Chadd
2013-12-06 17:32 ` Janusz Dziedzic
1 sibling, 0 replies; 14+ messages in thread
From: Adrian Chadd @ 2013-12-06 17:25 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: ath10k
For reference, STBC is not spatials treams, it's "space time block coding."
IIRC, the QCA hardware only does 1 stream STBC on two-stream or
three-stream devices.
-adrian
On 6 December 2013 08:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
> Hi,
>
> Recently, I've been making quite a lot of tests with two QWLE900V5-18 cards.
> I had some issues with the drivers (e.g. regarding the regulatory domain),
> but I've managed to fix them on my own. However, there is one issue that I
> cannot deal with.
> I'm trying to get the highest throughput possible using 3x3 MIMO. The
> problem is that the wifi card does not set higher rates than 2x433.3Mbps
> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
> have 3 spatial streams.
> First, I thought it is a problem with some options of hostapd, but hostapd
> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123] options.
> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
> disallows the 2x433.3Mbps link, which is another issue).
> Driver info shows that the driver should support 3 spatial streams.
> I am not sure where is the problem, is it some bug in hostapd, which forces
> the card to use 2 spatial streams only or is it the driver, which does not
> enable 3 streams when it is possible. The physical connectivity (antennas
> etc.) is not the problem AFAIK.
>
>
> The ath10k driver used for AP is a bit hacked to always report the US regd
> code
>
> Some dumps for you:
>
> iw version 3.13
>
> iw phy phy0 info
> Wiphy phy0
> max # scan SSIDs: 16
> max scan IEs length: 199 bytes
> Coverage class: 0 (up to 0m)
> Device supports AP-side u-APSD.
> Supported Ciphers:
> * WEP40 (00-0f-ac:1)
> * WEP104 (00-0f-ac:5)
> * TKIP (00-0f-ac:2)
> * CCMP (00-0f-ac:4)
> * CMAC (00-0f-ac:6)
> Available Antennas: TX 0 RX 0
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * monitor
> * P2P-client
> * P2P-GO
> Band 2:
> Capabilities: 0x19e3
> RX LDPC
> HT20/HT40
> Static SM Power Save
> RX HT20 SGI
> RX HT40 SGI
> TX STBC
> RX STBC 1-stream
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-23
> VHT Capabilities (0x338001b2):
> Max MPDU length: 11454
> Supported Channel Width: neither 160 nor 80+80
> RX LDPC
> short GI (80 MHz)
> TX STBC
> RX antenna pattern consistency
> VHT RX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: MCS 0-9
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT RX highest supported: 0 Mbps
> VHT TX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: MCS 0-9
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT TX highest supported: 0 Mbps
> Bitrates (non-HT):
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> Frequencies:
> * 5180 MHz [36] (20.0 dBm)
> * 5200 MHz [40] (20.0 dBm) (no IR)
> * 5220 MHz [44] (20.0 dBm)
> * 5240 MHz [48] (20.0 dBm) (no IR)
> * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
> DFS state: usable (for 110543 sec)
> * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
> DFS state: usable (for 110543 sec)
> * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
> DFS state: usable (for 110543 sec)
> * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
> DFS state: usable (for 110543 sec)
> * 5500 MHz [100] (disabled)
> * 5520 MHz [104] (disabled)
> * 5540 MHz [108] (disabled)
> * 5560 MHz [112] (disabled)
> * 5580 MHz [116] (disabled)
> * 5600 MHz [120] (disabled)
> * 5620 MHz [124] (disabled)
> * 5640 MHz [128] (disabled)
> * 5660 MHz [132] (disabled)
> * 5680 MHz [136] (disabled)
> * 5700 MHz [140] (disabled)
> * 5745 MHz [149] (disabled)
> * 5765 MHz [153] (disabled)
> * 5785 MHz [157] (disabled)
> * 5805 MHz [161] (disabled)
> * 5825 MHz [165] (disabled)
> Supported commands:
> * new_interface
> * set_interface
> * new_key
> * start_ap
> * new_station
> * new_mpath
> * set_mesh_config
> * set_bss
> * authenticate
> * associate
> * deauthenticate
> * disassociate
> * join_ibss
> * join_mesh
> * remain_on_channel
> * set_tx_bitrate_mask
> * frame
> * frame_wait_cancel
> * set_wiphy_netns
> * set_channel
> * set_wds_peer
> * probe_client
> * set_noack_map
> * register_beacons
> * start_p2p_device
> * set_mcast_rate
> * connect
> * disconnect
> Supported TX frame types:
> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
> 0xd0 0xe0 0xf0
> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
> 0xd0 0xe0 0xf0
> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0
> 0xe0 0xf0
> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
> 0xd0 0xe0 0xf0
> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
> 0xc0 0xd0 0xe0 0xf0
> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
> 0xc0 0xd0 0xe0 0xf0
> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
> 0xd0 0xe0 0xf0
> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
> 0xc0 0xd0 0xe0 0xf0
> Supported RX frame types:
> * IBSS: 0x40 0xb0 0xc0 0xd0
> * managed: 0x40 0xd0
> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * mesh point: 0xb0 0xc0 0xd0
> * P2P-client: 0x40 0xd0
> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * P2P-device: 0x40 0xd0
> software interface modes (can always be added):
> * AP/VLAN
> * monitor
> valid interface combinations:
> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{ AP } <= 7,
> total <= 8, #channels <= 1, STA/AP BI must match
> HT Capability overrides:
> * MCS: ff ff ff ff ff ff ff ff ff ff
> * maximum A-MSDU length
> * supported channel width
> * short GI for 40 MHz
> * max A-MPDU length exponent
> * min MPDU start spacing
> Device supports TX status socket option.
> Device supports HT-IBSS.
> Device supports scan flush.
>
>
> hostapd --version
> hostapd v2.1-devel
>
>
> dmesg (AP)
> [ 4808.976236 <tel:%5B%204808.976236>] Loading modules backported from Linux
> version next-20131129-0-gae5be52
> [ 4808.976243 <tel:%5B%204808.976243>] Backport generated by backports.git
> backports-20131129-0-g8a36e16
> [ 4808.982669 <tel:%5B%204808.982669>] cfg80211: Calling CRDA to update
> world regulatory domain
> [ 4810.814727] ath10k_pci 0000:06:00.0: BAR 0: assigned [mem
> 0xf7200000-0xf73fffff 64bit]
> [ 4810.819406] ath10k: MSI-X didn't succeed (1), trying MSI
> [ 4810.819480] ath10k_pci 0000:06:00.0: irq 49 for MSI/MSI-X
> [ 4810.819513] ath10k: MSI interrupt handling
> [ 4810.861220] ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> [ 4811.749751] ath10k: UART prints disabled
> [ 4811.756642] ath10k: firmware 10.1.389 booted
> [ 4811.766282] ath10k: htt target version 2.1
> [ 4811.767324] ath: EEPROM regdomain: 0x60
> [ 4811.767328] ath: EEPROM indicates we should expect a direct regpair map
> [ 4811.767333] ath: Country alpha2 being used: h7
> [ 4811.767336] ath: Regpair used: 0x60
> [ 4811.782155] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>
>
> dmesg (STA)
> [110825.598266] Loading modules backported from Linux version
> next-20131129-0-gae5be52
> [110825.598271] Backport generated by backports.git
> backports-20131129-0-g8a36e16
> [110825.603361] cfg80211: Calling CRDA to update world regulatory domain
> [110827.515449] ath10k_pci 0000:0c:00.0: BAR 0: assigned [mem
> 0xece00000-0xecffffff 64bit]
> [110827.515883] ath10k: MSI-X didn't succeed (1), trying MSI
> [110827.516037] ath10k_pci 0000:0c:00.0: irq 47 for MSI/MSI-X
> [110827.516114] ath10k: MSI interrupt handling
> [110827.561579] ath10k: Hardware name qca988x hw2.0 version 0x4100016c
> [110828.778794] ath10k: UART prints disabled
> [110828.785405] ath10k: firmware 999.999.0.636 booted
> [110828.795890] ath10k: htt target version 2.1
> [110828.797409] ath: EEPROM regdomain: 0x0
> [110828.797413] ath: EEPROM indicates default country code should be used
> [110828.797417] ath: doing EEPROM country->regdmn map search
> [110828.797422] ath: country maps to regdmn code: 0x3a
> [110828.797426] ath: Country alpha2 being
>
> BR,
>
> --
> Tomasz Tajmajer,
> Embedded Systems Engineer,
> Elnovel Sp. z o.o. [Ltd.] (elnovel.com)
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-06 16:33 [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link Tomasz Tajmajer
2013-12-06 17:25 ` Adrian Chadd
@ 2013-12-06 17:32 ` Janusz Dziedzic
2013-12-09 9:04 ` Kalle Valo
1 sibling, 1 reply; 14+ messages in thread
From: Janusz Dziedzic @ 2013-12-06 17:32 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: ath10k
On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
> Hi,
>
> Recently, I've been making quite a lot of tests with two QWLE900V5-18 cards.
> I had some issues with the drivers (e.g. regarding the regulatory domain),
> but I've managed to fix them on my own. However, there is one issue that I
> cannot deal with.
> I'm trying to get the highest throughput possible using 3x3 MIMO. The
> problem is that the wifi card does not set higher rates than 2x433.3Mbps
> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
> have 3 spatial streams.
> First, I thought it is a problem with some options of hostapd, but hostapd
> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123] options.
> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
> disallows the 2x433.3Mbps link, which is another issue).
> Driver info shows that the driver should support 3 spatial streams.
> I am not sure where is the problem, is it some bug in hostapd, which forces
> the card to use 2 spatial streams only or is it the driver, which does not
> enable 3 streams when it is possible. The physical connectivity (antennas
> etc.) is not the problem AFAIK.
>
When sta assoc to ap you will get dbg mesg (you can enable this eg.
when loading ath10k_core module with param - debug_mask).
"mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
Also
rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be interesting
- unfortunetly we don't print this.
But you can print this.
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-06 17:32 ` Janusz Dziedzic
@ 2013-12-09 9:04 ` Kalle Valo
2013-12-09 10:03 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Kalle Valo @ 2013-12-09 9:04 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: Tomasz Tajmajer, ath10k
Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>> Hi,
>>
>> Recently, I've been making quite a lot of tests with two QWLE900V5-18 cards.
>> I had some issues with the drivers (e.g. regarding the regulatory domain),
>> but I've managed to fix them on my own. However, there is one issue that I
>> cannot deal with.
>> I'm trying to get the highest throughput possible using 3x3 MIMO. The
>> problem is that the wifi card does not set higher rates than 2x433.3Mbps
>> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
>> have 3 spatial streams.
>> First, I thought it is a problem with some options of hostapd, but hostapd
>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123] options.
>> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
>> disallows the 2x433.3Mbps link, which is another issue).
>> Driver info shows that the driver should support 3 spatial streams.
>> I am not sure where is the problem, is it some bug in hostapd, which forces
>> the card to use 2 spatial streams only or is it the driver, which does not
>> enable 3 streams when it is possible. The physical connectivity (antennas
>> etc.) is not the problem AFAIK.
>>
>
> When sta assoc to ap you will get dbg mesg (you can enable this eg.
> when loading ath10k_core module with param - debug_mask).
> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
This debug message is enabled with ATH10K_DBG_MAC. More info here:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug
> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
> interesting - unfortunetly we don't print this. But you can print
> this.
Indeed, we should include that to the message as well.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-09 9:04 ` Kalle Valo
@ 2013-12-09 10:03 ` Tomasz Tajmajer
2013-12-09 10:13 ` Michal Kazior
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-09 10:03 UTC (permalink / raw)
To: ath10k
On 09.12.2013 10:04, Kalle Valo wrote:
> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>
>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>> Hi,
>>>
>>> Recently, I've been making quite a lot of tests with two QWLE900V5-18 cards.
>>> I had some issues with the drivers (e.g. regarding the regulatory domain),
>>> but I've managed to fix them on my own. However, there is one issue that I
>>> cannot deal with.
>>> I'm trying to get the highest throughput possible using 3x3 MIMO. The
>>> problem is that the wifi card does not set higher rates than 2x433.3Mbps
>>> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
>>> have 3 spatial streams.
>>> First, I thought it is a problem with some options of hostapd, but hostapd
>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123] options.
>>> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
>>> disallows the 2x433.3Mbps link, which is another issue).
>>> Driver info shows that the driver should support 3 spatial streams.
>>> I am not sure where is the problem, is it some bug in hostapd, which forces
>>> the card to use 2 spatial streams only or is it the driver, which does not
>>> enable 3 streams when it is possible. The physical connectivity (antennas
>>> etc.) is not the problem AFAIK.
>>>
>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>> when loading ath10k_core module with param - debug_mask).
>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>
> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>
>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>> interesting - unfortunetly we don't print this. But you can print
>> this.
> Indeed, we should include that to the message as well.
>
I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
suggested.
Here is the output for STA:
[ 2278.320312] ath10k: htt target version 2.1
[ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2 subtype 0
[ 2278.320741] ath10k: mac vdev 0 cts_prot 0
[ 2278.320765] ath10k: mac vdev 0 slot_time 1
[ 2278.320801] ath10k: mac vdev 0 preamble 1n
[ 2278.321320] ath10k: mac config channel 5180 mhz
[ 2278.321353] ath10k: mac vdev 0 psmode disable
[ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 2278.321458] ath10k: mac vdev 0 psmode disable
[ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
[ 2282.499946] ath10k: mac config channel 5180 mhz
[ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
[ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
[ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
[ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
[ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
[ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
[ 2282.709096] wlan1: authenticated
[ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
[ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
status=0 aid=1)
[ 2282.714331] ath10k: mac vdev 0 dtim_period 2
[ 2282.714367] ath10k: mac vdev 0 slot_time 2
[ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
[ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535
flags 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
[ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
[ 2282.714435] ath10k: mac vdev 0 up (associated) bssid
04:f0:21:0c:a2:3a aid 1
[ 2282.714822] ath10k: mac vdev 0 psmode enable
[ 2282.714869] wlan1: associated
And for AP:
[ 9460.458700] ath10k: htt target version 2.1
[ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1 subtype 0
[ 9460.459120] ath10k: mac vdev 0 cts_prot 0
[ 9460.459155] ath10k: mac vdev 0 slot_time 1
[ 9460.459156] ath10k: mac vdev 0 preamble 1n
[ 9460.459385] ath10k: mac config channel 5180 mhz
[ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[ 9461.562262] ath10k: mac vdev 0 rts threshold -1
[ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
[ 9461.564900] ath10k: mac config channel 5180 mhz
[ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
[ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
[ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
[ 9461.571970] ath10k: mac vdev 0 up
[ 9461.572108] ath10k: mac vdev 0 cts_prot 0
[ 9461.572117] ath10k: mac vdev 0 slot_time 2
[ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[ 9461.572192] ath10k: mac vdev 0 preamble 1n
[ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
[ 9549.331637] ath10k: mac vdev 0 cts_prot 0
[ 9549.331644] ath10k: mac vdev 0 preamble 1n
[ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new sta)
[ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
[ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
[ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu 1048575
flags 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
[ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
As you can see, the "nss" value is set to 3, but I've never observed
VHT-NSS 3 reported by "iw DEV station dump". Also the maximum throughput
for UDP measured by iperf was ~630Mbps, which seems to be the netto
value for 2x433 Mbps PHY throughput.
Do you have any idea what may be wrong ?
Br,
--
Tomasz Tajmajer,
Embedded Systems Engineer,
Elnovel Sp. z o.o. [Ltd.] (elnovel.com)
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-09 10:03 ` Tomasz Tajmajer
@ 2013-12-09 10:13 ` Michal Kazior
2013-12-09 11:29 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Michal Kazior @ 2013-12-09 10:13 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: ath10k
On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>
> On 09.12.2013 10:04, Kalle Valo wrote:
>>
>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>
>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Recently, I've been making quite a lot of tests with two QWLE900V5-18
>>>> cards.
>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>> domain),
>>>> but I've managed to fix them on my own. However, there is one issue that
>>>> I
>>>> cannot deal with.
>>>> I'm trying to get the highest throughput possible using 3x3 MIMO. The
>>>> problem is that the wifi card does not set higher rates than 2x433.3Mbps
>>>> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
>>>> have 3 spatial streams.
>>>> First, I thought it is a problem with some options of hostapd, but
>>>> hostapd
>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>> options.
>>>> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>> Driver info shows that the driver should support 3 spatial streams.
>>>> I am not sure where is the problem, is it some bug in hostapd, which
>>>> forces
>>>> the card to use 2 spatial streams only or is it the driver, which does
>>>> not
>>>> enable 3 streams when it is possible. The physical connectivity
>>>> (antennas
>>>> etc.) is not the problem AFAIK.
>>>>
>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>> when loading ath10k_core module with param - debug_mask).
>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>
>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>
>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>
>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>> interesting - unfortunetly we don't print this. But you can print
>>> this.
>>
>> Indeed, we should include that to the message as well.
>>
>
> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
> suggested.
> Here is the output for STA:
>
> [ 2278.320312] ath10k: htt target version 2.1
> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2 subtype 0
> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
> [ 2278.321320] ath10k: mac config channel 5180 mhz
> [ 2278.321353] ath10k: mac vdev 0 psmode disable
> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 2278.321458] ath10k: mac vdev 0 psmode disable
> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
> [ 2282.499946] ath10k: mac config channel 5180 mhz
> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
> [ 2282.709096] wlan1: authenticated
> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
> status=0 aid=1)
> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535 flags
> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid 04:f0:21:0c:a2:3a
> aid 1
> [ 2282.714822] ath10k: mac vdev 0 psmode enable
> [ 2282.714869] wlan1: associated
>
> And for AP:
> [ 9460.458700] ath10k: htt target version 2.1
> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1 subtype 0
> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
> [ 9460.459385] ath10k: mac config channel 5180 mhz
> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
> [ 9461.564900] ath10k: mac config channel 5180 mhz
> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
> [ 9461.571970] ath10k: mac vdev 0 up
> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new sta)
> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu 1048575 flags
> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>
>
> As you can see, the "nss" value is set to 3, but I've never observed VHT-NSS
> 3 reported by "iw DEV station dump". Also the maximum throughput for UDP
> measured by iperf was ~630Mbps, which seems to be the netto value for 2x433
> Mbps PHY throughput.
I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
are broken due to FW limitation).
You can create a monitor interface on the receiver side and run
wireshark in non-promiscuous mode and check radiotap headers to
confirm whether 3 spatial streams are used or not.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-09 10:13 ` Michal Kazior
@ 2013-12-09 11:29 ` Tomasz Tajmajer
2013-12-09 12:10 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-09 11:29 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
[-- Attachment #1: Type: text/plain, Size: 6561 bytes --]
On 09.12.2013 11:13, Michal Kazior wrote:
> On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>> On 09.12.2013 10:04, Kalle Valo wrote:
>>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>>
>>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>> Hi,
>>>>>
>>>>> Recently, I've been making quite a lot of tests with two QWLE900V5-18
>>>>> cards.
>>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>>> domain),
>>>>> but I've managed to fix them on my own. However, there is one issue that
>>>>> I
>>>>> cannot deal with.
>>>>> I'm trying to get the highest throughput possible using 3x3 MIMO. The
>>>>> problem is that the wifi card does not set higher rates than 2x433.3Mbps
>>>>> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
>>>>> have 3 spatial streams.
>>>>> First, I thought it is a problem with some options of hostapd, but
>>>>> hostapd
>>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>>> options.
>>>>> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
>>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>>> Driver info shows that the driver should support 3 spatial streams.
>>>>> I am not sure where is the problem, is it some bug in hostapd, which
>>>>> forces
>>>>> the card to use 2 spatial streams only or is it the driver, which does
>>>>> not
>>>>> enable 3 streams when it is possible. The physical connectivity
>>>>> (antennas
>>>>> etc.) is not the problem AFAIK.
>>>>>
>>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>>> when loading ath10k_core module with param - debug_mask).
>>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>>
>>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>>
>>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>>> interesting - unfortunetly we don't print this. But you can print
>>>> this.
>>> Indeed, we should include that to the message as well.
>>>
>> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
>> suggested.
>> Here is the output for STA:
>>
>> [ 2278.320312] ath10k: htt target version 2.1
>> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2 subtype 0
>> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
>> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
>> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
>> [ 2278.321320] ath10k: mac config channel 5180 mhz
>> [ 2278.321353] ath10k: mac vdev 0 psmode disable
>> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 2278.321458] ath10k: mac vdev 0 psmode disable
>> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
>> [ 2282.499946] ath10k: mac config channel 5180 mhz
>> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
>> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
>> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
>> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
>> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
>> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
>> [ 2282.709096] wlan1: authenticated
>> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
>> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
>> status=0 aid=1)
>> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
>> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
>> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
>> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535 flags
>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
>> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid 04:f0:21:0c:a2:3a
>> aid 1
>> [ 2282.714822] ath10k: mac vdev 0 psmode enable
>> [ 2282.714869] wlan1: associated
>>
>> And for AP:
>> [ 9460.458700] ath10k: htt target version 2.1
>> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1 subtype 0
>> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
>> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
>> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
>> [ 9460.459385] ath10k: mac config channel 5180 mhz
>> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
>> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
>> [ 9461.564900] ath10k: mac config channel 5180 mhz
>> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
>> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
>> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode 11ac-vht80
>> [ 9461.571970] ath10k: mac vdev 0 up
>> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
>> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
>> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
>> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
>> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
>> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
>> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
>> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new sta)
>> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
>> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
>> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu 1048575 flags
>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>>
>>
>> As you can see, the "nss" value is set to 3, but I've never observed VHT-NSS
>> 3 reported by "iw DEV station dump". Also the maximum throughput for UDP
>> measured by iperf was ~630Mbps, which seems to be the netto value for 2x433
>> Mbps PHY throughput.
> I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
> are broken due to FW limitation).
>
> You can create a monitor interface on the receiver side and run
> wireshark in non-promiscuous mode and check radiotap headers to
> confirm whether 3 spatial streams are used or not.
>
>
> Michał
>
I've attached the output from wireshark.
Bandwidth: 80 MHz (4)
User 0: MCS 9
1001 .... = MCS index 0: 9 (256-QAM 5/6)
.... 0010 = Spatial streams 0: 2
Space-time streams 0: 2
Coding 0: BCC (0)
[Data Rate: 866,6 Mb/s]
Unfortunately, it confirms that only 2 spatial streams are used.
TomaszT
[-- Attachment #2: 80211ac_packet_dump.txt --]
[-- Type: text/plain, Size: 5581 bytes --]
No. Time Source Destination Protocol Length Info
185396 4.169737000 10.0.10.2 10.0.10.1 UDP 1562 Source port: commplex-link Destination port: commplex-link
Frame 185396: 1562 bytes on wire (12496 bits), 1562 bytes captured (12496 bits) on interface 0
Radiotap Header v0, Length 30
Header revision: 0
Header pad: 0
Header length: 30
Present flags
.... .... .... .... .... .... .... ...0 = TSFT: False
.... .... .... .... .... .... .... ..1. = Flags: True
.... .... .... .... .... .... .... .0.. = Rate: False
.... .... .... .... .... .... .... 1... = Channel: True
.... .... .... .... .... .... ...0 .... = FHSS: False
.... .... .... .... .... .... ..1. .... = dBm Antenna Signal: True
.... .... .... .... .... .... .0.. .... = dBm Antenna Noise: False
.... .... .... .... .... .... 0... .... = Lock Quality: False
.... .... .... .... .... ...0 .... .... = TX Attenuation: False
.... .... .... .... .... ..0. .... .... = dB TX Attenuation: False
.... .... .... .... .... .0.. .... .... = dBm TX Power: False
.... .... .... .... .... 1... .... .... = Antenna: True
.... .... .... .... ...0 .... .... .... = dB Antenna Signal: False
.... .... .... .... ..0. .... .... .... = dB Antenna Noise: False
.... .... .... .... .1.. .... .... .... = RX flags: True
.... .... .... .0.. .... .... .... .... = Channel+: False
.... .... .... 0... .... .... .... .... = HT information: False
.... .... ...0 .... .... .... .... .... = A-MPDU Status: False
.... .... ..1. .... .... .... .... .... = VHT information: True
...0 0000 00.. .... .... .... .... .... = Reserved: 0x00000000
..0. .... .... .... .... .... .... .... = Radiotap NS next: False
.0.. .... .... .... .... .... .... .... = Vendor NS next: False
0... .... .... .... .... .... .... .... = Ext: False
Flags: 0x00
.... ...0 = CFP: False
.... ..0. = Preamble: Long
.... .0.. = WEP: False
.... 0... = Fragmentation: False
...0 .... = FCS at end: False
..0. .... = Data Pad: False
.0.. .... = Bad FCS: False
0... .... = Short GI: False
Channel frequency: 5180 [A 36]
Channel type: 802.11a (0x0140)
.... .... ...0 .... = Turbo: False
.... .... ..0. .... = Complementary Code Keying (CCK): False
.... .... .1.. .... = Orthogonal Frequency-Division Multiplexing (OFDM): True
.... .... 0... .... = 2 GHz spectrum: False
.... ...1 .... .... = 5 GHz spectrum: True
.... ..0. .... .... = Passive: False
.... .0.. .... .... = Dynamic CCK-OFDM: False
.... 0... .... .... = Gaussian Frequency Shift Keying (GFSK): False
...0 .... .... .... = GSM (900MHz): False
..0. .... .... .... = Static Turbo: False
.0.. .... .... .... = Half Rate Channel (10MHz Channel Width): False
0... .... .... .... = Quarter Rate Channel (5MHz Channel Width): False
SSI Signal: -32 dBm
Antenna: 0
RX flags: 0x0000
.... .... .... .... .... ..0. = Bad PLCP: False
VHT information
Known VHT information: 0x44
.... .... .... ...0 = STBC: False
.... .... .... ..0. = TXOP_PS_NOT_ALLOWED: False
.... .... .... .1.. = Guard interval: True
.... .... .... 0... = SGI Nsym disambiguation: False
.... .... ...0 .... = LDPC extra OFDM symbol: False
.... .... ..0. .... = Beamformed: False
.... .... .1.. .... = Bandwidth: True
.... .... 0... .... = Group ID: False
.... ...0 .... .... = Partial AID: False
.... .1.. = Guard interval: short (1)
Bandwidth: 80 MHz (4)
User 0: MCS 9
1001 .... = MCS index 0: 9 (256-QAM 5/6)
.... 0010 = Spatial streams 0: 2
Space-time streams 0: 2
Coding 0: BCC (0)
[Data Rate: 866,6 Mb/s]
IEEE 802.11 QoS Data, Flags: .......T
Type/Subtype: QoS Data (0x28)
Frame Control Field: 0x8801
.... ..00 = Version: 0
.... 10.. = Type: Data frame (2)
1000 .... = Subtype: 8
Flags: 0x01
.... ..01 = DS status: Frame from STA to DS via an AP (To DS: 1 From DS: 0) (0x01)
.... .0.. = More Fragments: This is the last fragment
.... 0... = Retry: Frame is not being retransmitted
...0 .... = PWR MGT: STA will stay up
..0. .... = More Data: No data buffered
.0.. .... = Protected flag: Data is not protected
0... .... = Order flag: Not strictly ordered
.000 0000 0011 0000 = Duration: 48 microseconds
Receiver address: CompexPt_0c:a2:3a (04:f0:21:0c:a2:3a)
BSS Id: CompexPt_0c:a2:3a (04:f0:21:0c:a2:3a)
Transmitter address: CompexPt_0c:a2:3b (04:f0:21:0c:a2:3b)
Source address: CompexPt_0c:a2:3b (04:f0:21:0c:a2:3b)
Destination address: CompexPt_0c:a2:3a (04:f0:21:0c:a2:3a)
Fragment number: 0
Sequence number: 931
Qos Control: 0x0000
.... .... .... 0000 = TID: 0
[.... .... .... .000 = Priority: Best Effort (Best Effort) (0)]
.... .... ...0 .... = QoS bit 4: Bits 8-15 of QoS Control field are TXOP Duration Requested
.... .... .00. .... = Ack Policy: Normal Ack (0x0000)
.... .... 0... .... = Payload Type: MSDU
0000 0000 .... .... = TXOP Duration Requested: 0 (no TXOP requested)
[-- 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] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-09 11:29 ` Tomasz Tajmajer
@ 2013-12-09 12:10 ` Tomasz Tajmajer
2013-12-11 12:19 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-09 12:10 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
On 09.12.2013 12:29, Tomasz Tajmajer wrote:
>
> On 09.12.2013 11:13, Michal Kazior wrote:
>> On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>> On 09.12.2013 10:04, Kalle Valo wrote:
>>>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>>>
>>>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Recently, I've been making quite a lot of tests with two
>>>>>> QWLE900V5-18
>>>>>> cards.
>>>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>>>> domain),
>>>>>> but I've managed to fix them on my own. However, there is one
>>>>>> issue that
>>>>>> I
>>>>>> cannot deal with.
>>>>>> I'm trying to get the highest throughput possible using 3x3 MIMO.
>>>>>> The
>>>>>> problem is that the wifi card does not set higher rates than
>>>>>> 2x433.3Mbps
>>>>>> (MCS 9, VHT-NSS 2). The specification says that it should be
>>>>>> possible to
>>>>>> have 3 spatial streams.
>>>>>> First, I thought it is a problem with some options of hostapd, but
>>>>>> hostapd
>>>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>>>> options.
>>>>>> Only [RX-STBC-1] may be set in the configuration (what in fact,
>>>>>> does not
>>>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>>>> Driver info shows that the driver should support 3 spatial streams.
>>>>>> I am not sure where is the problem, is it some bug in hostapd, which
>>>>>> forces
>>>>>> the card to use 2 spatial streams only or is it the driver, which
>>>>>> does
>>>>>> not
>>>>>> enable 3 streams when it is possible. The physical connectivity
>>>>>> (antennas
>>>>>> etc.) is not the problem AFAIK.
>>>>>>
>>>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>>>> when loading ath10k_core module with param - debug_mask).
>>>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>>>
>>>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>>>
>>>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>>>> interesting - unfortunetly we don't print this. But you can print
>>>>> this.
>>>> Indeed, we should include that to the message as well.
>>>>
>>> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
>>> suggested.
>>> Here is the output for STA:
>>>
>>> [ 2278.320312] ath10k: htt target version 2.1
>>> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2
>>> subtype 0
>>> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
>>> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
>>> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
>>> [ 2278.321320] ath10k: mac config channel 5180 mhz
>>> [ 2278.321353] ath10k: mac vdev 0 psmode disable
>>> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>> [ 2278.321458] ath10k: mac vdev 0 psmode disable
>>> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
>>> [ 2282.499946] ath10k: mac config channel 5180 mhz
>>> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
>>> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
>>> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
>>> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode
>>> 11ac-vht80
>>> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
>>> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
>>> [ 2282.709096] wlan1: authenticated
>>> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
>>> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
>>> status=0 aid=1)
>>> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
>>> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
>>> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
>>> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535
>>> flags
>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
>>> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid
>>> 04:f0:21:0c:a2:3a
>>> aid 1
>>> [ 2282.714822] ath10k: mac vdev 0 psmode enable
>>> [ 2282.714869] wlan1: associated
>>>
>>> And for AP:
>>> [ 9460.458700] ath10k: htt target version 2.1
>>> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1
>>> subtype 0
>>> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
>>> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
>>> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
>>> [ 9460.459385] ath10k: mac config channel 5180 mhz
>>> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>>> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
>>> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
>>> [ 9461.564900] ath10k: mac config channel 5180 mhz
>>> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
>>> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
>>> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode
>>> 11ac-vht80
>>> [ 9461.571970] ath10k: mac vdev 0 up
>>> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
>>> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
>>> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
>>> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
>>> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
>>> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
>>> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
>>> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new
>>> sta)
>>> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
>>> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
>>> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu
>>> 1048575 flags
>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>>>
>>>
>>> As you can see, the "nss" value is set to 3, but I've never observed
>>> VHT-NSS
>>> 3 reported by "iw DEV station dump". Also the maximum throughput for
>>> UDP
>>> measured by iperf was ~630Mbps, which seems to be the netto value
>>> for 2x433
>>> Mbps PHY throughput.
>> I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
>> are broken due to FW limitation).
>>
>> You can create a monitor interface on the receiver side and run
>> wireshark in non-promiscuous mode and check radiotap headers to
>> confirm whether 3 spatial streams are used or not.
>>
>>
>> Michał
>>
> I've attached the output from wireshark.
>
> Bandwidth: 80 MHz (4)
> User 0: MCS 9
> 1001 .... = MCS index 0: 9 (256-QAM 5/6)
> .... 0010 = Spatial streams 0: 2
> Space-time streams 0: 2
> Coding 0: BCC (0)
> [Data Rate: 866,6 Mb/s]
>
> Unfortunately, it confirms that only 2 spatial streams are used.
>
>
> TomaszT
>
I thought that maybe one of the card is physically damaged and the third
spatial link cannot be established. I've checked that using a 802.11ac
router, which I also have (and it supports 3 streams). Both cards
connected with it using only 2 spatial streams. Its unlikely that both
cards have a malfunction, so its rather a software problem.
TomaszT
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-09 12:10 ` Tomasz Tajmajer
@ 2013-12-11 12:19 ` Tomasz Tajmajer
2013-12-11 19:43 ` Janusz Dziedzic
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-11 12:19 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
On 09.12.2013 13:10, Tomasz Tajmajer wrote:
>
> On 09.12.2013 12:29, Tomasz Tajmajer wrote:
>>
>> On 09.12.2013 11:13, Michal Kazior wrote:
>>> On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>> On 09.12.2013 10:04, Kalle Valo wrote:
>>>>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>>>>
>>>>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Recently, I've been making quite a lot of tests with two
>>>>>>> QWLE900V5-18
>>>>>>> cards.
>>>>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>>>>> domain),
>>>>>>> but I've managed to fix them on my own. However, there is one
>>>>>>> issue that
>>>>>>> I
>>>>>>> cannot deal with.
>>>>>>> I'm trying to get the highest throughput possible using 3x3
>>>>>>> MIMO. The
>>>>>>> problem is that the wifi card does not set higher rates than
>>>>>>> 2x433.3Mbps
>>>>>>> (MCS 9, VHT-NSS 2). The specification says that it should be
>>>>>>> possible to
>>>>>>> have 3 spatial streams.
>>>>>>> First, I thought it is a problem with some options of hostapd, but
>>>>>>> hostapd
>>>>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>>>>> options.
>>>>>>> Only [RX-STBC-1] may be set in the configuration (what in fact,
>>>>>>> does not
>>>>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>>>>> Driver info shows that the driver should support 3 spatial streams.
>>>>>>> I am not sure where is the problem, is it some bug in hostapd,
>>>>>>> which
>>>>>>> forces
>>>>>>> the card to use 2 spatial streams only or is it the driver,
>>>>>>> which does
>>>>>>> not
>>>>>>> enable 3 streams when it is possible. The physical connectivity
>>>>>>> (antennas
>>>>>>> etc.) is not the problem AFAIK.
>>>>>>>
>>>>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>>>>> when loading ath10k_core module with param - debug_mask).
>>>>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>>>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>>>>
>>>>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>>>>
>>>>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>>>>> interesting - unfortunetly we don't print this. But you can print
>>>>>> this.
>>>>> Indeed, we should include that to the message as well.
>>>>>
>>>> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
>>>> suggested.
>>>> Here is the output for STA:
>>>>
>>>> [ 2278.320312] ath10k: htt target version 2.1
>>>> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2
>>>> subtype 0
>>>> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
>>>> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
>>>> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
>>>> [ 2278.321320] ath10k: mac config channel 5180 mhz
>>>> [ 2278.321353] ath10k: mac vdev 0 psmode disable
>>>> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>> [ 2278.321458] ath10k: mac vdev 0 psmode disable
>>>> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
>>>> [ 2282.499946] ath10k: mac config channel 5180 mhz
>>>> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
>>>> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
>>>> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
>>>> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>> 11ac-vht80
>>>> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
>>>> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
>>>> [ 2282.709096] wlan1: authenticated
>>>> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
>>>> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
>>>> status=0 aid=1)
>>>> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
>>>> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
>>>> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
>>>> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu
>>>> 65535 flags
>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
>>>> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid
>>>> 04:f0:21:0c:a2:3a
>>>> aid 1
>>>> [ 2282.714822] ath10k: mac vdev 0 psmode enable
>>>> [ 2282.714869] wlan1: associated
>>>>
>>>> And for AP:
>>>> [ 9460.458700] ath10k: htt target version 2.1
>>>> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1
>>>> subtype 0
>>>> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
>>>> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
>>>> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
>>>> [ 9460.459385] ath10k: mac config channel 5180 mhz
>>>> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>>>> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
>>>> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
>>>> [ 9461.564900] ath10k: mac config channel 5180 mhz
>>>> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
>>>> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
>>>> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>> 11ac-vht80
>>>> [ 9461.571970] ath10k: mac vdev 0 up
>>>> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
>>>> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
>>>> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes
>>>> ready
>>>> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
>>>> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
>>>> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
>>>> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
>>>> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b
>>>> (new sta)
>>>> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
>>>> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
>>>> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu
>>>> 1048575 flags
>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>>>>
>>>>
>>>> As you can see, the "nss" value is set to 3, but I've never
>>>> observed VHT-NSS
>>>> 3 reported by "iw DEV station dump". Also the maximum throughput
>>>> for UDP
>>>> measured by iperf was ~630Mbps, which seems to be the netto value
>>>> for 2x433
>>>> Mbps PHY throughput.
>>> I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
>>> are broken due to FW limitation).
>>>
>>> You can create a monitor interface on the receiver side and run
>>> wireshark in non-promiscuous mode and check radiotap headers to
>>> confirm whether 3 spatial streams are used or not.
>>>
>>>
>>> Michał
>>>
>> I've attached the output from wireshark.
>>
>> Bandwidth: 80 MHz (4)
>> User 0: MCS 9
>> 1001 .... = MCS index 0: 9 (256-QAM 5/6)
>> .... 0010 = Spatial streams 0: 2
>> Space-time streams 0: 2
>> Coding 0: BCC (0)
>> [Data Rate: 866,6 Mb/s]
>>
>> Unfortunately, it confirms that only 2 spatial streams are used.
>>
>>
>> TomaszT
>>
> I thought that maybe one of the card is physically damaged and the
> third spatial link cannot be established. I've checked that using a
> 802.11ac router, which I also have (and it supports 3 streams). Both
> cards connected with it using only 2 spatial streams. Its unlikely
> that both cards have a malfunction, so its rather a software problem.
>
> TomaszT
Hi,
Are there any chances, that this issue would be investigated and
hopefully fixed before the end of the year ?
BR,
TomaszT
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-11 12:19 ` Tomasz Tajmajer
@ 2013-12-11 19:43 ` Janusz Dziedzic
2013-12-11 19:51 ` Janusz Dziedzic
0 siblings, 1 reply; 14+ messages in thread
From: Janusz Dziedzic @ 2013-12-11 19:43 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: Michal Kazior, ath10k
On 11 December 2013 13:19, Tomasz Tajmajer <tt@elnovel.com> wrote:
>
> On 09.12.2013 13:10, Tomasz Tajmajer wrote:
>>
>>
>> On 09.12.2013 12:29, Tomasz Tajmajer wrote:
>>>
>>>
>>> On 09.12.2013 11:13, Michal Kazior wrote:
>>>>
>>>> On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>
>>>>> On 09.12.2013 10:04, Kalle Valo wrote:
>>>>>>
>>>>>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>>>>>
>>>>>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Recently, I've been making quite a lot of tests with two
>>>>>>>> QWLE900V5-18
>>>>>>>> cards.
>>>>>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>>>>>> domain),
>>>>>>>> but I've managed to fix them on my own. However, there is one issue
>>>>>>>> that
>>>>>>>> I
>>>>>>>> cannot deal with.
>>>>>>>> I'm trying to get the highest throughput possible using 3x3 MIMO.
>>>>>>>> The
>>>>>>>> problem is that the wifi card does not set higher rates than
>>>>>>>> 2x433.3Mbps
>>>>>>>> (MCS 9, VHT-NSS 2). The specification says that it should be
>>>>>>>> possible to
>>>>>>>> have 3 spatial streams.
>>>>>>>> First, I thought it is a problem with some options of hostapd, but
>>>>>>>> hostapd
>>>>>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>>>>>> options.
>>>>>>>> Only [RX-STBC-1] may be set in the configuration (what in fact, does
>>>>>>>> not
>>>>>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>>>>>> Driver info shows that the driver should support 3 spatial streams.
>>>>>>>> I am not sure where is the problem, is it some bug in hostapd, which
>>>>>>>> forces
>>>>>>>> the card to use 2 spatial streams only or is it the driver, which
>>>>>>>> does
>>>>>>>> not
>>>>>>>> enable 3 streams when it is possible. The physical connectivity
>>>>>>>> (antennas
>>>>>>>> etc.) is not the problem AFAIK.
>>>>>>>>
>>>>>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>>>>>> when loading ath10k_core module with param - debug_mask).
>>>>>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>>>>>
>>>>>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>>>>>
>>>>>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>>>>>
>>>>>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>>>>>> interesting - unfortunetly we don't print this. But you can print
>>>>>>> this.
>>>>>>
>>>>>> Indeed, we should include that to the message as well.
>>>>>>
>>>>> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
>>>>> suggested.
>>>>> Here is the output for STA:
>>>>>
>>>>> [ 2278.320312] ath10k: htt target version 2.1
>>>>> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2 subtype
>>>>> 0
>>>>> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
>>>>> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
>>>>> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
>>>>> [ 2278.321320] ath10k: mac config channel 5180 mhz
>>>>> [ 2278.321353] ath10k: mac vdev 0 psmode disable
>>>>> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>>> [ 2278.321458] ath10k: mac vdev 0 psmode disable
>>>>> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
>>>>> [ 2282.499946] ath10k: mac config channel 5180 mhz
>>>>> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
>>>>> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
>>>>> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
>>>>> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>>> 11ac-vht80
>>>>> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
>>>>> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
>>>>> [ 2282.709096] wlan1: authenticated
>>>>> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
>>>>> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
>>>>> status=0 aid=1)
>>>>> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
>>>>> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
>>>>> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
>>>>> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535
>>>>> flags
>>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>>> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
>>>>> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid
>>>>> 04:f0:21:0c:a2:3a
>>>>> aid 1
>>>>> [ 2282.714822] ath10k: mac vdev 0 psmode enable
>>>>> [ 2282.714869] wlan1: associated
>>>>>
>>>>> And for AP:
>>>>> [ 9460.458700] ath10k: htt target version 2.1
>>>>> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1 subtype
>>>>> 0
>>>>> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
>>>>> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
>>>>> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
>>>>> [ 9460.459385] ath10k: mac config channel 5180 mhz
>>>>> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>>>>> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
>>>>> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
>>>>> [ 9461.564900] ath10k: mac config channel 5180 mhz
>>>>> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
>>>>> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
>>>>> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>>> 11ac-vht80
>>>>> [ 9461.571970] ath10k: mac vdev 0 up
>>>>> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
>>>>> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
>>>>> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
>>>>> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
>>>>> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
>>>>> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
>>>>> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
>>>>> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new
>>>>> sta)
>>>>> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
>>>>> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
>>>>> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu 1048575
>>>>> flags
>>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>>> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>>>>>
>>>>>
>>>>> As you can see, the "nss" value is set to 3, but I've never observed
>>>>> VHT-NSS
>>>>> 3 reported by "iw DEV station dump". Also the maximum throughput for
>>>>> UDP
>>>>> measured by iperf was ~630Mbps, which seems to be the netto value for
>>>>> 2x433
>>>>> Mbps PHY throughput.
>>>>
>>>> I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
>>>> are broken due to FW limitation).
>>>>
>>>> You can create a monitor interface on the receiver side and run
>>>> wireshark in non-promiscuous mode and check radiotap headers to
>>>> confirm whether 3 spatial streams are used or not.
>>>>
>>>>
>>>> Michał
>>>>
>>> I've attached the output from wireshark.
>>>
>>> Bandwidth: 80 MHz (4)
>>> User 0: MCS 9
>>> 1001 .... = MCS index 0: 9 (256-QAM 5/6)
>>> .... 0010 = Spatial streams 0: 2
>>> Space-time streams 0: 2
>>> Coding 0: BCC (0)
>>> [Data Rate: 866,6 Mb/s]
>>>
>>> Unfortunately, it confirms that only 2 spatial streams are used.
>>>
>>>
>>> TomaszT
>>>
>> I thought that maybe one of the card is physically damaged and the third
>> spatial link cannot be established. I've checked that using a 802.11ac
>> router, which I also have (and it supports 3 streams). Both cards connected
>> with it using only 2 spatial streams. Its unlikely that both cards have a
>> malfunction, so its rather a software problem.
>>
>> TomaszT
>
> Hi,
>
> Are there any chances, that this issue would be investigated and hopefully
> fixed before the end of the year ?
>
Seems from driver we configure everything correctly. Rate Control is
in FW - so FW will decide what NSS/MCS to use. Here we see our devices
works fine with 3x3.
BTW.
You can try to use fixed_rate setting. You will have to apply some
patches from mac80211-next/group:
Kernel:
1) nl80211: don't clear bitrate_mask twice
2) nl80211: back to default bitrate_mask correctly
3) nl80211/cfg80211: bitrate_mask, rename mcs to ht_mcs
4) nl80211: add VHT support for set_bitrate_mask
5) ath10k: add set_bitrate_mask callback - this I will send in few minutes
iw:
1) iw: add VHT MCS/NSS set support to set bitrates
After that just run ap and: iw wlanX set bitrates legacy-5 ht-mcs-5
vht-mcs-5 3:0
You should send frames from AP with NSS=3, MCS=0
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-11 19:43 ` Janusz Dziedzic
@ 2013-12-11 19:51 ` Janusz Dziedzic
2013-12-12 11:42 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Janusz Dziedzic @ 2013-12-11 19:51 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: Michal Kazior, ath10k
On 11 December 2013 20:43, Janusz Dziedzic <janusz.dziedzic@tieto.com> wrote:
> On 11 December 2013 13:19, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>
>> On 09.12.2013 13:10, Tomasz Tajmajer wrote:
>>>
>>>
>>> On 09.12.2013 12:29, Tomasz Tajmajer wrote:
>>>>
>>>>
>>>> On 09.12.2013 11:13, Michal Kazior wrote:
>>>>>
>>>>> On 9 December 2013 11:03, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>>
>>>>>> On 09.12.2013 10:04, Kalle Valo wrote:
>>>>>>>
>>>>>>> Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
>>>>>>>
>>>>>>>> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Recently, I've been making quite a lot of tests with two
>>>>>>>>> QWLE900V5-18
>>>>>>>>> cards.
>>>>>>>>> I had some issues with the drivers (e.g. regarding the regulatory
>>>>>>>>> domain),
>>>>>>>>> but I've managed to fix them on my own. However, there is one issue
>>>>>>>>> that
>>>>>>>>> I
>>>>>>>>> cannot deal with.
>>>>>>>>> I'm trying to get the highest throughput possible using 3x3 MIMO.
>>>>>>>>> The
>>>>>>>>> problem is that the wifi card does not set higher rates than
>>>>>>>>> 2x433.3Mbps
>>>>>>>>> (MCS 9, VHT-NSS 2). The specification says that it should be
>>>>>>>>> possible to
>>>>>>>>> have 3 spatial streams.
>>>>>>>>> First, I thought it is a problem with some options of hostapd, but
>>>>>>>>> hostapd
>>>>>>>>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123]
>>>>>>>>> options.
>>>>>>>>> Only [RX-STBC-1] may be set in the configuration (what in fact, does
>>>>>>>>> not
>>>>>>>>> disallows the 2x433.3Mbps link, which is another issue).
>>>>>>>>> Driver info shows that the driver should support 3 spatial streams.
>>>>>>>>> I am not sure where is the problem, is it some bug in hostapd, which
>>>>>>>>> forces
>>>>>>>>> the card to use 2 spatial streams only or is it the driver, which
>>>>>>>>> does
>>>>>>>>> not
>>>>>>>>> enable 3 streams when it is possible. The physical connectivity
>>>>>>>>> (antennas
>>>>>>>>> etc.) is not the problem AFAIK.
>>>>>>>>>
>>>>>>>> When sta assoc to ap you will get dbg mesg (you can enable this eg.
>>>>>>>> when loading ath10k_core module with param - debug_mask).
>>>>>>>> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
>>>>>>>
>>>>>>> This debug message is enabled with ATH10K_DBG_MAC. More info here:
>>>>>>>
>>>>>>> http://wireless.kernel.org/en/users/Drivers/ath10k/debug
>>>>>>>
>>>>>>>> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
>>>>>>>> interesting - unfortunetly we don't print this. But you can print
>>>>>>>> this.
>>>>>>>
>>>>>>> Indeed, we should include that to the message as well.
>>>>>>>
>>>>>> I've enabled dbg messages and added rx_mcs_set and tx_mcs_set as you
>>>>>> suggested.
>>>>>> Here is the output for STA:
>>>>>>
>>>>>> [ 2278.320312] ath10k: htt target version 2.1
>>>>>> [ 2278.320455] ath10k: mac vdev create 0 (add interface) type 2 subtype
>>>>>> 0
>>>>>> [ 2278.320741] ath10k: mac vdev 0 cts_prot 0
>>>>>> [ 2278.320765] ath10k: mac vdev 0 slot_time 1
>>>>>> [ 2278.320801] ath10k: mac vdev 0 preamble 1n
>>>>>> [ 2278.321320] ath10k: mac config channel 5180 mhz
>>>>>> [ 2278.321353] ath10k: mac vdev 0 psmode disable
>>>>>> [ 2278.321448] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>>>>>> [ 2278.321458] ath10k: mac vdev 0 psmode disable
>>>>>> [ 2282.499925] wlan1: authenticate with 04:f0:21:0c:a2:3a
>>>>>> [ 2282.499946] ath10k: mac config channel 5180 mhz
>>>>>> [ 2282.499962] ath10k: mac vdev 0 beacon_interval 100
>>>>>> [ 2282.499968] ath10k: mac vdev 0 create peer 04:f0:21:0c:a2:3a
>>>>>> [ 2282.500109] ath10k: mac vdev 0 start 04:f0:21:0c:a2:3a
>>>>>> [ 2282.500115] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>>>> 11ac-vht80
>>>>>> [ 2282.506711] wlan1: direct probe to 04:f0:21:0c:a2:3a (try 1/3)
>>>>>> [ 2282.708052] wlan1: send auth to 04:f0:21:0c:a2:3a (try 2/3)
>>>>>> [ 2282.709096] wlan1: authenticated
>>>>>> [ 2282.712122] wlan1: associate with 04:f0:21:0c:a2:3a (try 1/3)
>>>>>> [ 2282.713907] wlan1: RX AssocResp from 04:f0:21:0c:a2:3a (capab=0x1
>>>>>> status=0 aid=1)
>>>>>> [ 2282.714331] ath10k: mac vdev 0 dtim_period 2
>>>>>> [ 2282.714367] ath10k: mac vdev 0 slot_time 2
>>>>>> [ 2282.714415] ath10k: mac ht peer 04:f0:21:0c:a2:3a mcs cnt 24 nss 3
>>>>>> [ 2282.714421] ath10k: mac vht peer 04:f0:21:0c:a2:3a max_mpdu 65535
>>>>>> flags
>>>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>>>> [ 2282.714427] ath10k: mac peer 04:f0:21:0c:a2:3a phymode 11ac-vht80
>>>>>> [ 2282.714435] ath10k: mac vdev 0 up (associated) bssid
>>>>>> 04:f0:21:0c:a2:3a
>>>>>> aid 1
>>>>>> [ 2282.714822] ath10k: mac vdev 0 psmode enable
>>>>>> [ 2282.714869] wlan1: associated
>>>>>>
>>>>>> And for AP:
>>>>>> [ 9460.458700] ath10k: htt target version 2.1
>>>>>> [ 9460.458874] ath10k: mac vdev create 0 (add interface) type 1 subtype
>>>>>> 0
>>>>>> [ 9460.459120] ath10k: mac vdev 0 cts_prot 0
>>>>>> [ 9460.459155] ath10k: mac vdev 0 slot_time 1
>>>>>> [ 9460.459156] ath10k: mac vdev 0 preamble 1n
>>>>>> [ 9460.459385] ath10k: mac config channel 5180 mhz
>>>>>> [ 9460.459434] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
>>>>>> [ 9461.562262] ath10k: mac vdev 0 rts threshold -1
>>>>>> [ 9461.562292] ath10k: mac vdev 0 fragmentation threshold -1
>>>>>> [ 9461.564900] ath10k: mac config channel 5180 mhz
>>>>>> [ 9461.564919] ath10k: mac vdev 0 beacon_interval 100
>>>>>> [ 9461.564923] ath10k: vdev 0 set beacon tx mode to staggered
>>>>>> [ 9461.564931] ath10k: mac vdev 0 start center_freq 5180 phymode
>>>>>> 11ac-vht80
>>>>>> [ 9461.571970] ath10k: mac vdev 0 up
>>>>>> [ 9461.572108] ath10k: mac vdev 0 cts_prot 0
>>>>>> [ 9461.572117] ath10k: mac vdev 0 slot_time 2
>>>>>> [ 9461.572241] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
>>>>>> [ 9461.572192] ath10k: mac vdev 0 preamble 1n
>>>>>> [ 9549.331556] ath10k: vdev 0 set beacon tx mode to staggered
>>>>>> [ 9549.331637] ath10k: mac vdev 0 cts_prot 0
>>>>>> [ 9549.331644] ath10k: mac vdev 0 preamble 1n
>>>>>> [ 9549.332425] ath10k: mac vdev 0 peer create 04:f0:21:0c:a2:3b (new
>>>>>> sta)
>>>>>> [ 9549.332628] ath10k: mac sta 04:f0:21:0c:a2:3b associated
>>>>>> [ 9549.332637] ath10k: mac ht peer 04:f0:21:0c:a2:3b mcs cnt 24 nss 3
>>>>>> [ 9549.332643] ath10k: mac vht peer 04:f0:21:0c:a2:3b max_mpdu 1048575
>>>>>> flags
>>>>>> 0x601b001 rx_mcs_set 0000ffea tx_mcs_set 0000ffea
>>>>>> [ 9549.332648] ath10k: mac peer 04:f0:21:0c:a2:3b phymode 11ac-vht80
>>>>>>
>>>>>>
>>>>>> As you can see, the "nss" value is set to 3, but I've never observed
>>>>>> VHT-NSS
>>>>>> 3 reported by "iw DEV station dump". Also the maximum throughput for
>>>>>> UDP
>>>>>> measured by iperf was ~630Mbps, which seems to be the netto value for
>>>>>> 2x433
>>>>>> Mbps PHY throughput.
>>>>>
>>>>> I wouldn't rely on station dump Tx/Rx stats (especially Tx stats which
>>>>> are broken due to FW limitation).
>>>>>
>>>>> You can create a monitor interface on the receiver side and run
>>>>> wireshark in non-promiscuous mode and check radiotap headers to
>>>>> confirm whether 3 spatial streams are used or not.
>>>>>
>>>>>
>>>>> Michał
>>>>>
>>>> I've attached the output from wireshark.
>>>>
>>>> Bandwidth: 80 MHz (4)
>>>> User 0: MCS 9
>>>> 1001 .... = MCS index 0: 9 (256-QAM 5/6)
>>>> .... 0010 = Spatial streams 0: 2
>>>> Space-time streams 0: 2
>>>> Coding 0: BCC (0)
>>>> [Data Rate: 866,6 Mb/s]
>>>>
>>>> Unfortunately, it confirms that only 2 spatial streams are used.
>>>>
>>>>
>>>> TomaszT
>>>>
>>> I thought that maybe one of the card is physically damaged and the third
>>> spatial link cannot be established. I've checked that using a 802.11ac
>>> router, which I also have (and it supports 3 streams). Both cards connected
>>> with it using only 2 spatial streams. Its unlikely that both cards have a
>>> malfunction, so its rather a software problem.
>>>
>>> TomaszT
>>
>> Hi,
>>
>> Are there any chances, that this issue would be investigated and hopefully
>> fixed before the end of the year ?
>>
> Seems from driver we configure everything correctly. Rate Control is
> in FW - so FW will decide what NSS/MCS to use. Here we see our devices
> works fine with 3x3.
>
> BTW.
> You can try to use fixed_rate setting. You will have to apply some
> patches from mac80211-next/group:
>
> Kernel:
> 1) nl80211: don't clear bitrate_mask twice
> 2) nl80211: back to default bitrate_mask correctly
> 3) nl80211/cfg80211: bitrate_mask, rename mcs to ht_mcs
> 4) nl80211: add VHT support for set_bitrate_mask
> 5) ath10k: add set_bitrate_mask callback - this I will send in few minutes
>
> iw:
> 1) iw: add VHT MCS/NSS set support to set bitrates
>
> After that just run ap and: iw wlanX set bitrates legacy-5 ht-mcs-5
> vht-mcs-5 3:0
>
> You should send frames from AP with NSS=3, MCS=0
>
BTW Do you have same problem with HT, or only with VHT?
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-11 19:51 ` Janusz Dziedzic
@ 2013-12-12 11:42 ` Tomasz Tajmajer
2013-12-12 15:01 ` Tomasz Tajmajer
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-12 11:42 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: Michal Kazior, ath10k
On 11.12.2013 20:51, Janusz Dziedzic wrote:
>> Seems from driver we configure everything correctly. Rate Control is
>> in FW - so FW will decide what NSS/MCS to use. Here we see our devices
>> works fine with 3x3.
>>
>> BTW.
>> You can try to use fixed_rate setting. You will have to apply some
>> patches from mac80211-next/group:
>>
>> Kernel:
>> 1) nl80211: don't clear bitrate_mask twice
>> 2) nl80211: back to default bitrate_mask correctly
>> 3) nl80211/cfg80211: bitrate_mask, rename mcs to ht_mcs
>> 4) nl80211: add VHT support for set_bitrate_mask
>> 5) ath10k: add set_bitrate_mask callback - this I will send in few minutes
>>
>> iw:
>> 1) iw: add VHT MCS/NSS set support to set bitrates
>>
>> After that just run ap and: iw wlanX set bitrates legacy-5 ht-mcs-5
>> vht-mcs-5 3:0
>>
>> You should send frames from AP with NSS=3, MCS=0
>>
> BTW Do you have same problem with HT, or only with VHT?
>
> BR
> Janusz
>
For HT 3x3 MIMO is working fine. The issue occurs only for VHT.
Thank you for your suggestions, I'll apply the patches and try to force
3 spatial streams manually. Hope it will work.
BTW: Which firmware and driver versions you were using in your tests ?
BR
TomaszT
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-12 11:42 ` Tomasz Tajmajer
@ 2013-12-12 15:01 ` Tomasz Tajmajer
2013-12-13 6:17 ` Michal Kazior
0 siblings, 1 reply; 14+ messages in thread
From: Tomasz Tajmajer @ 2013-12-12 15:01 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: Michal Kazior, ath10k
On 12.12.2013 12:42, Tomasz Tajmajer wrote:
>
> On 11.12.2013 20:51, Janusz Dziedzic wrote:
>>> Seems from driver we configure everything correctly. Rate Control is
>>> in FW - so FW will decide what NSS/MCS to use. Here we see our devices
>>> works fine with 3x3.
>>>
>>> BTW.
>>> You can try to use fixed_rate setting. You will have to apply some
>>> patches from mac80211-next/group:
>>>
>>> Kernel:
>>> 1) nl80211: don't clear bitrate_mask twice
>>> 2) nl80211: back to default bitrate_mask correctly
>>> 3) nl80211/cfg80211: bitrate_mask, rename mcs to ht_mcs
>>> 4) nl80211: add VHT support for set_bitrate_mask
>>> 5) ath10k: add set_bitrate_mask callback - this I will send in few
>>> minutes
>>>
>>> iw:
>>> 1) iw: add VHT MCS/NSS set support to set bitrates
>>>
>>> After that just run ap and: iw wlanX set bitrates legacy-5 ht-mcs-5
>>> vht-mcs-5 3:0
>>>
>>> You should send frames from AP with NSS=3, MCS=0
>>>
>> BTW Do you have same problem with HT, or only with VHT?
>>
>> BR
>> Janusz
>>
>
> For HT 3x3 MIMO is working fine. The issue occurs only for VHT.
>
> Thank you for your suggestions, I'll apply the patches and try to
> force 3 spatial streams manually. Hope it will work.
>
> BTW: Which firmware and driver versions you were using in your tests ?
>
> BR
> TomaszT
>
>
>
BTW: I get this trace very often on both AP and STA:
[ 870.512817] ------------[ cut here ]------------
[ 870.512835] WARNING: at
/.../backports-20131129/net/wireless/util.c:1066
cfg80211_calculate_bitrate+0x178/0x1e0 [cfg80211]()
[ 870.512836] Hardware name: MS-7850
[ 870.512837] Modules linked in: nls_iso8859_1(F) pci_stub(F)
vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) nvidia(POF)
arc4(F) coretemp(F) kvm_intel(F) snd_hda_codec_hdmi(F) kvm(F)
aesni_intel(F) ablk_helper(F) cryptd(F) lrw(F) aes_i586(F)
snd_hda_codec_realtek(F) snd_hda_intel(F) joydev(F) bnep(F) rfcomm(F)
snd_hda_codec(F) bluetooth(F) xts(F) ath10k_pci(OF) gf128mul(F)
ath10k_core(OF) snd_hwdep(F) snd_pcm(F) snd_seq_midi(F) snd_rawmidi(F)
ath(OF) snd_seq_midi_event(F) snd_seq(F) snd_timer(F) snd_seq_device(F)
mac80211(OF) snd(F) soundcore(F) cfg80211(OF) psmouse(F) serio_raw(F)
microcode(F) snd_page_alloc(F) compat(OF) mxm_wmi(F) mac_hid(F) mei(F)
shpchp(F) wmi(F) video(F) lpc_ich(F) parport_pc(F) ppdev(F) lp(F)
parport(F) usb_storage(F) raid10(F) raid456(F) async_pq(F) async_xor(F)
xor(F) async_memcpy(F) async_raid6_recov(F) hid_generic(F) usbhid(F)
hid(F) ahci(F) libahci(F) r8169(F) raid6_pq(F) async_tx(F) raid1(F)
raid0(F) multipath(F) linear(F)
[ 870.512870] Pid: 22186, comm: hostapd Tainted: PF O
3.8.0-33-generic #48~precise1-Ubuntu
[ 870.512872] Call Trace:
[ 870.512877] [<c104b8f2>] warn_slowpath_common+0x72/0xa0
[ 870.512883] [<f889c288>] ? cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 870.512889] [<f889c288>] ? cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 870.512891] [<c104b942>] warn_slowpath_null+0x22/0x30
[ 870.512897] [<f889c288>] cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 870.512904] [<f88a93e7>] nl80211_put_sta_rate+0x47/0x290 [cfg80211]
[ 870.512908] [<c1308742>] ? nla_put+0x32/0x50
[ 870.512915] [<f88a9a8f>] nl80211_send_station.isra.62+0x45f/0x810
[cfg80211]
[ 870.512921] [<f88aa264>] nl80211_get_station+0x1a4/0x270 [cfg80211]
[ 870.512928] [<f88a4430>] ? __cfg80211_rdev_from_attrs+0x190/0x190
[cfg80211]
[ 870.512931] [<c1563c6c>] genl_rcv_msg+0x1fc/0x270
[ 870.512936] [<c15350cb>] ? __alloc_skb+0x6b/0x260
[ 870.512938] [<c1563a70>] ? genl_rcv+0x30/0x30
[ 870.512939] [<c15634de>] netlink_rcv_skb+0x8e/0xb0
[ 870.512941] [<c1563a5c>] genl_rcv+0x1c/0x30
[ 870.512943] [<c1562e97>] netlink_unicast+0x177/0x1f0
[ 870.512944] [<c1563138>] netlink_sendmsg+0x228/0x390
[ 870.512947] [<c152acf1>] sock_sendmsg+0xd1/0xf0
[ 870.512950] [<c12f9432>] ? _copy_from_user+0x42/0x60
[ 870.512952] [<c1536bf4>] ? verify_iovec+0x44/0xb0
[ 870.512954] [<c152bfc2>] ___sys_sendmsg+0x262/0x270
[ 870.512956] [<c107e7a0>] ? default_wake_function+0x10/0x20
[ 870.512958] [<c1075da7>] ? __wake_up_common+0x47/0x70
[ 870.512961] [<c1152667>] ? kmem_cache_alloc+0x77/0x140
[ 870.512963] [<c10774b5>] ? __wake_up+0x45/0x60
[ 870.512965] [<c162dc6d>] ? _raw_spin_lock+0xd/0x10
[ 870.512967] [<c152a128>] ? sock_destroy_inode+0x28/0x30
[ 870.512969] [<c152a128>] ? sock_destroy_inode+0x28/0x30
[ 870.512971] [<c152a128>] ? sock_destroy_inode+0x28/0x30
[ 870.512973] [<c117b951>] ? destroy_inode+0x31/0x50
[ 870.512975] [<c117ba61>] ? evict+0xf1/0x170
[ 870.512977] [<c117c1bf>] ? iput_final+0xaf/0x130
[ 870.512979] [<c1176f88>] ? __d_free+0x38/0x60
[ 870.512981] [<c1176f88>] ? __d_free+0x38/0x60
[ 870.512983] [<c152ce8e>] __sys_sendmsg+0x3e/0x70
[ 870.512985] [<c152d588>] sys_socketcall+0x278/0x2d0
[ 870.512988] [<c1165c3d>] ? ____fput+0xd/0x10
[ 870.512990] [<c1069fd6>] ? task_work_run+0xb6/0xd0
[ 870.512993] [<c1012217>] ? do_notify_resume+0x97/0xa0
[ 870.512995] [<c163538d>] sysenter_do_call+0x12/0x28
[ 870.512997] [<c1620000>] ? ext3_orphan_cleanup.isra.85+0x145/0x27e
[ 870.512998] ---[ end trace c9ccbf9458ea0b81 ]---
[ 121.786233] ------------[ cut here ]------------
[ 121.786277] WARNING: at
/.../backports-20131129/net/wireless/util.c:1066
cfg80211_calculate_bitrate+0x178/0x1e0 [cfg80211]()
[ 121.786282] Hardware name: MXG061
[ 121.786286] Modules linked in: arc4(F) nvidia(POF) ath10k_pci(OF)
ath10k_core(OF) ath(OF) snd_hda_codec_idt(F) snd_hda_intel(F)
snd_hda_codec(F) mac80211(OF) r852(F) coretemp(F) gpio_ich(F)
sm_common(F) joydev(F) bnep(F) snd_hwdep(F) kvm_intel(F) snd_pcm(F)
cfg80211(OF) nand(F) snd_seq_midi(F) kvm(F) mtd(F) snd_rawmidi(F)
nand_ids(F) rfcomm(F) snd_seq_midi_event(F) snd_seq(F) nand_bch(F)
snd_timer(F) bluetooth(F) lpc_ich(F) r592(F) bch(F) snd_seq_device(F)
psmouse(F) snd(F) compat(OF) soundcore(F) nand_ecc(F) dell_laptop(F)
dell_wmi(F) memstick(F) serio_raw(F) snd_page_alloc(F) dcdbas(F)
sparse_keymap(F) microcode(F) wmi(F) mac_hid(F) video(F) parport_pc(F)
ppdev(F) lp(F) parport(F) raid10(F) raid456(F) async_pq(F) async_xor(F)
xor(F) async_memcpy(F) async_raid6_recov(F) firewire_ohci(F)
firewire_core(F) crc_itu_t(F) sdhci_pci(F) sdhci(F) tg3(F) ptp(F)
pps_core(F) raid6_pq(F) async_tx(F) raid1(F) raid0(F) multipath(F) linear(F)
[ 121.786430] Pid: 2395, comm: iwconfig Tainted: PF O
3.8.0-31-generic #46~precise1-Ubuntu
[ 121.786434] Call Trace:
[ 121.786449] [<c104b8b2>] warn_slowpath_common+0x72/0xa0
[ 121.786480] [<f8fcc288>] ? cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 121.786511] [<f8fcc288>] ? cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 121.786519] [<c104b902>] warn_slowpath_null+0x22/0x30
[ 121.786550] [<f8fcc288>] cfg80211_calculate_bitrate+0x178/0x1e0
[cfg80211]
[ 121.786590] [<f900e313>] cfg80211_wext_giwrate+0xc3/0x1a0 [cfg80211]
[ 121.786629] [<f901127d>] ? cfg80211_mgd_wext_giwap+0x4d/0x90 [cfg80211]
[ 121.786639] [<c15fe77d>] ioctl_standard_call+0x5d/0xe0
[ 121.786648] [<c15fe941>] wireless_process_ioctl.constprop.4+0x141/0x1a0
[ 121.786685] [<f900e250>] ? cfg80211_wext_giwtxpower+0x150/0x150
[cfg80211]
[ 121.786693] [<c15fe9fb>] wext_handle_ioctl+0x5b/0xd0
[ 121.786702] [<c1541dde>] dev_ioctl+0xbe/0x290
[ 121.786712] [<c152b4cb>] sock_ioctl+0x1ab/0x290
[ 121.786721] [<c152b320>] ? move_addr_to_user+0xb0/0xb0
[ 121.786729] [<c117422f>] do_vfs_ioctl+0x7f/0x2f0
[ 121.786739] [<c13ac290>] ? tty_write_lock+0x50/0x50
[ 121.786746] [<c1174510>] sys_ioctl+0x70/0x80
[ 121.786755] [<c1634e4d>] sysenter_do_call+0x12/0x28
[ 121.786760] ---[ end trace 3e19dfdb1f2646d7 ]---
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
2013-12-12 15:01 ` Tomasz Tajmajer
@ 2013-12-13 6:17 ` Michal Kazior
0 siblings, 0 replies; 14+ messages in thread
From: Michal Kazior @ 2013-12-13 6:17 UTC (permalink / raw)
To: Tomasz Tajmajer; +Cc: Janusz Dziedzic, ath10k
On 12 December 2013 16:01, Tomasz Tajmajer <tt@elnovel.com> wrote:
> BTW: I get this trace very often on both AP and STA:
>
> [ 870.512817] ------------[ cut here ]------------
> [ 870.512835] WARNING: at /.../backports-20131129/net/wireless/util.c:1066
> cfg80211_calculate_bitrate+0x178/0x1e0 [cfg80211]()
You're probably missing the following patches:
ath10k: clear tx status before submitting to mac80211
ath10k: fix Tx status clearing
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2013-12-13 6:17 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-06 16:33 [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link Tomasz Tajmajer
2013-12-06 17:25 ` Adrian Chadd
2013-12-06 17:32 ` Janusz Dziedzic
2013-12-09 9:04 ` Kalle Valo
2013-12-09 10:03 ` Tomasz Tajmajer
2013-12-09 10:13 ` Michal Kazior
2013-12-09 11:29 ` Tomasz Tajmajer
2013-12-09 12:10 ` Tomasz Tajmajer
2013-12-11 12:19 ` Tomasz Tajmajer
2013-12-11 19:43 ` Janusz Dziedzic
2013-12-11 19:51 ` Janusz Dziedzic
2013-12-12 11:42 ` Tomasz Tajmajer
2013-12-12 15:01 ` Tomasz Tajmajer
2013-12-13 6:17 ` Michal Kazior
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.