ath11k: QCN9074: low HE-MCS index

ath11k: QCN9074: low HE-MCS index

[Tanguy Serrat]

[-- Attachment #1: Type: text/plain, Size: 2398 bytes --]

Hi everyone,

In my quest to get 2x QCN9074 paired and achieving high throughput
data transfers, I am now facing issues with the AP configuration.

Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
apart) although SNR and RSSI are always very strong and supposedly in
specs (SNR > 40db or RSSI < -48db).

iw wlp6s0 link
Connected to 00:15:61:27:cd:dc (on wlp6s0)
SSID: Space
freq: 5745
RX: 1073584482 bytes (708567 packets)
TX: 355824214 bytes (256143 packets)
signal: -40 dBm
rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0

In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
get at least twice as much.

It seems to me that either mac80211, ath11k or hostapd are not
advertising the available capabilities correctly. I have tried setting
hostapd he_basic_mcs_set=65530 or others but did not help.

I have added ieee80211_regdom=FR option to cfg80211 module on the AP
side. Channel selection is done with ACS survey. I also tried other
channels/frequencies without success eg. 5500Mhz.

iw reg get
global
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country US: DFS-FCC
(2402 - 2472 @ 40), (6, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
(5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
(5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW

Current setup is:
- Intel x86
- Ubuntu 22.04
- Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
c60d15f389ef9832a8da410e438d81b10327751f)
with commit reverted from the bug ticket I opened
(https://bugzilla.kernel.org/show_bug.cgi?id=217536).
- 1x QCN9074 as AP, 1x as managed client 50cm apart
- Both AP and Client are running with the latest 2.7.0 FW.

I have started from this ticket
(https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
file, and adapted, please find attached.

Anyone seeing what could be my issue / how I could debug further ?

Thank you !
Tanguy

[-- Attachment #2: hostapd_ath11k.conf --]
[-- Type: application/octet-stream, Size: 1073 bytes --]

ctrl_interface=/var/run/hostapd
driver=nl80211
interface=wlp4s0
country_code=FR
#bridge=lbr0
ssid=Space
#ignore_broadcast_ssid=0
max_num_sta=256
dtim_period=4
wmm_enabled=1
ieee80211ax=1
ieee80211ac=1
ieee80211n=1
hw_mode=a
channel=0
he_oper_centr_freq_seg0_idx=
he_oper_chwidth=2

ieee80211d=1
ieee80211h=1
#freqlist=5500

he_su_beamformer=1
he_su_beamformee=1
he_mu_beamformer=1
#he_oper_centr_freq_seg0_idx=
#he_oper_centr_freq_seg1_idx=
he_bss_color=1
#he_default_pe_duration=0
#he_twt_required=0
#he_rts_threshold=0

#he_basic_mcs_nss_set=65530


ht_capab=[LDPC][SMPS-DYNAMIC][TX-STBC][RX-STBC-1][MAX-AMSDU-7935][DSSS_CCK-40][HT40+][SHORT-GI-40]
vht_capab=[MAX-MPDU-11454][VHT160-80PLUS80][RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][RX-STBC1][SU-BEAMFORMER][SOUNDING-DIMENSION-4][SU-BEAMFORMEE][MAX-A-MPDU-LEN-EXP7][MU-BEAMFORMER][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
auth_algs=1
wpa=2
wpa_key_mgmt=WPA-PSK  
wpa_pairwise=CCMP
ieee80211w=0
wpa_passphrase=12345678
#wps_independent=1
eap_server=1
#wps_state=2
#ap_setup_locked=0
#wps_rf_bands=a
#macaddr_acl=0

[-- Attachment #3: Type: text/plain, Size: 102 bytes --]

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Linux regression tracking (Thorsten Leemhuis)]

On 26.06.23 14:27, Tanguy Serrat wrote:
>
> In my quest to get 2x QCN9074 paired and achieving high throughput
> data transfers, I am now facing issues with the AP configuration.
> 
> Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
> apart) although SNR and RSSI are always very strong and supposedly in
> specs (SNR > 40db or RSSI < -48db).

FWIW for anyone seeing this that might wonder: yes, this is the same
issue that is already brought up on the lists here:

https://lore.kernel.org/all/1326a6e4-758d-3344-d90c-8a126748b034@gmail.com/

Sadly nothing much came from it (and coincidentally I tried to revive
that thread a few minutes after Tanguy Serrat sent the quoted mail,
which was an hour before I saw it -- aka: race condition). Well, maybe
one of these mails hopefully will help.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot ^backmonitor: d90c-8a126748b034@gmail.com/

> iw wlp6s0 link
> Connected to 00:15:61:27:cd:dc (on wlp6s0)
> SSID: Space
> freq: 5745
> RX: 1073584482 bytes (708567 packets)
> TX: 355824214 bytes (256143 packets)
> signal: -40 dBm
> rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> 
> In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
> get at least twice as much.
> 
> It seems to me that either mac80211, ath11k or hostapd are not
> advertising the available capabilities correctly. I have tried setting
> hostapd he_basic_mcs_set=65530 or others but did not help.
> 
> I have added ieee80211_regdom=FR option to cfg80211 module on the AP
> side. Channel selection is done with ACS survey. I also tried other
> channels/frequencies without success eg. 5500Mhz.
> 
> iw reg get
> global
> country FR: DFS-ETSI
> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> (5725 - 5875 @ 80), (N/A, 13), (N/A)
> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> (57000 - 71000 @ 2160), (N/A, 40), (N/A)
> 
> phy#0 (self-managed)
> country US: DFS-FCC
> (2402 - 2472 @ 40), (6, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> (5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
> 
> Current setup is:
> - Intel x86
> - Ubuntu 22.04
> - Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
> c60d15f389ef9832a8da410e438d81b10327751f)
> with commit reverted from the bug ticket I opened
> (https://bugzilla.kernel.org/show_bug.cgi?id=217536).
> - 1x QCN9074 as AP, 1x as managed client 50cm apart
> - Both AP and Client are running with the latest 2.7.0 FW.
> 
> I have started from this ticket
> (https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
> file, and adapted, please find attached.
> 
> Anyone seeing what could be my issue / how I could debug further ?
> 
> Thank you !
> Tanguy
> 
> 

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Tanguy Serrat]

> FWIW for anyone seeing this that might wonder: yes, this is the same
> issue that is already brought up on the lists here:

> https://lore.kernel.org/all/1326a6e4-758d-3344-d90c-8a126748b034@gmail.com/

Thank you Thorsten. This is a separate new issue. I have opened a new
ticket here with my latest findings:
https://bugzilla.kernel.org/show_bug.cgi?id=217652

Any help would be greatly appreciated, this is quite blocking in our
product development.


Le lun. 26 juin 2023 à 15:50, Linux regression tracking (Thorsten
Leemhuis) <regressions@leemhuis.info> a écrit :
>
> On 26.06.23 14:27, Tanguy Serrat wrote:
> >
> > In my quest to get 2x QCN9074 paired and achieving high throughput
> > data transfers, I am now facing issues with the AP configuration.
> >
> > Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
> > apart) although SNR and RSSI are always very strong and supposedly in
> > specs (SNR > 40db or RSSI < -48db).
>
> FWIW for anyone seeing this that might wonder: yes, this is the same
> issue that is already brought up on the lists here:
>
> https://lore.kernel.org/all/1326a6e4-758d-3344-d90c-8a126748b034@gmail.com/
>
> Sadly nothing much came from it (and coincidentally I tried to revive
> that thread a few minutes after Tanguy Serrat sent the quoted mail,
> which was an hour before I saw it -- aka: race condition). Well, maybe
> one of these mails hopefully will help.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot ^backmonitor: d90c-8a126748b034@gmail.com/
>
> > iw wlp6s0 link
> > Connected to 00:15:61:27:cd:dc (on wlp6s0)
> > SSID: Space
> > freq: 5745
> > RX: 1073584482 bytes (708567 packets)
> > TX: 355824214 bytes (256143 packets)
> > signal: -40 dBm
> > rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> > tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> >
> > In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
> > get at least twice as much.
> >
> > It seems to me that either mac80211, ath11k or hostapd are not
> > advertising the available capabilities correctly. I have tried setting
> > hostapd he_basic_mcs_set=65530 or others but did not help.
> >
> > I have added ieee80211_regdom=FR option to cfg80211 module on the AP
> > side. Channel selection is done with ACS survey. I also tried other
> > channels/frequencies without success eg. 5500Mhz.
> >
> > iw reg get
> > global
> > country FR: DFS-ETSI
> > (2400 - 2483 @ 40), (N/A, 20), (N/A)
> > (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> > (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> > (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> > (5725 - 5875 @ 80), (N/A, 13), (N/A)
> > (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> > (57000 - 71000 @ 2160), (N/A, 40), (N/A)
> >
> > phy#0 (self-managed)
> > country US: DFS-FCC
> > (2402 - 2472 @ 40), (6, 30), (N/A)
> > (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> > (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> > (5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
> >
> > Current setup is:
> > - Intel x86
> > - Ubuntu 22.04
> > - Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
> > c60d15f389ef9832a8da410e438d81b10327751f)
> > with commit reverted from the bug ticket I opened
> > (https://bugzilla.kernel.org/show_bug.cgi?id=217536).
> > - 1x QCN9074 as AP, 1x as managed client 50cm apart
> > - Both AP and Client are running with the latest 2.7.0 FW.
> >
> > I have started from this ticket
> > (https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
> > file, and adapted, please find attached.
> >
> > Anyone seeing what could be my issue / how I could debug further ?
> >
> > Thank you !
> > Tanguy
> >
> >

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Thorsten Leemhuis]

[CCing Manikanta Pubbisetty, the author of the culprit; and Kalle, but
just for the record, as he afaik is unavailable for some time ]

On 10.07.23 13:01, Tanguy Serrat wrote:
>> FWIW for anyone seeing this that might wonder: yes, this is the same
>> issue that is already brought up on the lists here:
> 
>> https://lore.kernel.org/all/1326a6e4-758d-3344-d90c-8a126748b034@gmail.com/
> 
> Thank you Thorsten. This is a separate new issue. I have opened a new
> ticket here with my latest findings:
> https://bugzilla.kernel.org/show_bug.cgi?id=217652

Sorry, I didn't notice, it was somewhat confusing from the outside. If
you report the same issue to both the list and bugzilla please interlink
them clearly near the top.

> Any help would be greatly appreciated, this is quite blocking in our
> product development.

Sounds like this thread aka
https://bugzilla.kernel.org/show_bug.cgi?id=217652 are not a regression.
If that's not correct please state so, but if it is: sorry, then I'm out
of here, I only try to ensure that regressions are fixed, everything
else is up to the regular developers of the code in question.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.


> Le lun. 26 juin 2023 à 15:50, Linux regression tracking (Thorsten
> Leemhuis) <regressions@leemhuis.info> a écrit :
>>
>> On 26.06.23 14:27, Tanguy Serrat wrote:
>>>
>>> In my quest to get 2x QCN9074 paired and achieving high throughput
>>> data transfers, I am now facing issues with the AP configuration.
>>>
>>> Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
>>> apart) although SNR and RSSI are always very strong and supposedly in
>>> specs (SNR > 40db or RSSI < -48db).
>>
>> FWIW for anyone seeing this that might wonder: yes, this is the same
>> issue that is already brought up on the lists here:
>>
>> https://lore.kernel.org/all/1326a6e4-758d-3344-d90c-8a126748b034@gmail.com/
>>
>> Sadly nothing much came from it (and coincidentally I tried to revive
>> that thread a few minutes after Tanguy Serrat sent the quoted mail,
>> which was an hour before I saw it -- aka: race condition). Well, maybe
>> one of these mails hopefully will help.
>>
>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>> --
>> Everything you wanna know about Linux kernel regression tracking:
>> https://linux-regtracking.leemhuis.info/about/#tldr
>> If I did something stupid, please tell me, as explained on that page.
>>
>> #regzbot ^backmonitor: d90c-8a126748b034@gmail.com/
>>
>>> iw wlp6s0 link
>>> Connected to 00:15:61:27:cd:dc (on wlp6s0)
>>> SSID: Space
>>> freq: 5745
>>> RX: 1073584482 bytes (708567 packets)
>>> TX: 355824214 bytes (256143 packets)
>>> signal: -40 dBm
>>> rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
>>> tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
>>>
>>> In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
>>> get at least twice as much.
>>>
>>> It seems to me that either mac80211, ath11k or hostapd are not
>>> advertising the available capabilities correctly. I have tried setting
>>> hostapd he_basic_mcs_set=65530 or others but did not help.
>>>
>>> I have added ieee80211_regdom=FR option to cfg80211 module on the AP
>>> side. Channel selection is done with ACS survey. I also tried other
>>> channels/frequencies without success eg. 5500Mhz.
>>>
>>> iw reg get
>>> global
>>> country FR: DFS-ETSI
>>> (2400 - 2483 @ 40), (N/A, 20), (N/A)
>>> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
>>> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>>> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
>>> (5725 - 5875 @ 80), (N/A, 13), (N/A)
>>> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
>>> (57000 - 71000 @ 2160), (N/A, 40), (N/A)
>>>
>>> phy#0 (self-managed)
>>> country US: DFS-FCC
>>> (2402 - 2472 @ 40), (6, 30), (N/A)
>>> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
>>> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
>>> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
>>> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
>>> (5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
>>>
>>> Current setup is:
>>> - Intel x86
>>> - Ubuntu 22.04
>>> - Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
>>> c60d15f389ef9832a8da410e438d81b10327751f)
>>> with commit reverted from the bug ticket I opened
>>> (https://bugzilla.kernel.org/show_bug.cgi?id=217536).
>>> - 1x QCN9074 as AP, 1x as managed client 50cm apart
>>> - Both AP and Client are running with the latest 2.7.0 FW.
>>>
>>> I have started from this ticket
>>> (https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
>>> file, and adapted, please find attached.
>>>
>>> Anyone seeing what could be my issue / how I could debug further ?
>>>
>>> Thank you !
>>> Tanguy
>>>
>>>
> 
> 

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Kalle Valo]

Tanguy Serrat <tanguy@squaremind.io> writes:

> Hi everyone,
>
> In my quest to get 2x QCN9074 paired and achieving high throughput
> data transfers, I am now facing issues with the AP configuration.
>
> Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
> apart) although SNR and RSSI are always very strong and supposedly in
> specs (SNR > 40db or RSSI < -48db).
>
> iw wlp6s0 link
> Connected to 00:15:61:27:cd:dc (on wlp6s0)
> SSID: Space
> freq: 5745
> RX: 1073584482 bytes (708567 packets)
> TX: 355824214 bytes (256143 packets)
> signal: -40 dBm
> rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
>
> In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
> get at least twice as much.
>
> It seems to me that either mac80211, ath11k or hostapd are not
> advertising the available capabilities correctly. I have tried setting
> hostapd he_basic_mcs_set=65530 or others but did not help.
>
> I have added ieee80211_regdom=FR option to cfg80211 module on the AP
> side. Channel selection is done with ACS survey. I also tried other
> channels/frequencies without success eg. 5500Mhz.
>
> iw reg get
> global
> country FR: DFS-ETSI
> (2400 - 2483 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> (5725 - 5875 @ 80), (N/A, 13), (N/A)
> (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> (57000 - 71000 @ 2160), (N/A, 40), (N/A)
>
> phy#0 (self-managed)
> country US: DFS-FCC
> (2402 - 2472 @ 40), (6, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> (5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
>
> Current setup is:
> - Intel x86
> - Ubuntu 22.04
> - Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
> c60d15f389ef9832a8da410e438d81b10327751f)
> with commit reverted from the bug ticket I opened
> (https://bugzilla.kernel.org/show_bug.cgi?id=217536).
> - 1x QCN9074 as AP, 1x as managed client 50cm apart
> - Both AP and Client are running with the latest 2.7.0 FW.
>
> I have started from this ticket
> (https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
> file, and adapted, please find attached.
>
> Anyone seeing what could be my issue / how I could debug further ?

As a start please file this to bugzilla as a new bug. Always one issue
per report, please. Otherwise it's a nightmare to manage the bug
reports.

https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport

Try to provide as much as information as you can to the report. You said
that you have tested it 50 cm apart but have you tested it, for example,
3 m apart? Please also include your full kernel .config file and dmesg
output.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Tanguy Serrat]

Dear Kalle,

Thank you for your reply.

I have opened two separate issues:
1) https://bugzilla.kernel.org/show_bug.cgi?id=217536 - related to a
previous issue I encountered.

2) https://bugzilla.kernel.org/show_bug.cgi?id=217652 - related to this feed.

I have tested 3m apart, as described in 217652, results are just
slightly better in terms of reported MCS. I still seem to be missing
all capabilities over 7.
I have attached the full dmesg log and .config file to the bug report

Le mar. 11 juil. 2023 à 08:49, Kalle Valo <kvalo@kernel.org> a écrit :
>
> Tanguy Serrat <tanguy@squaremind.io> writes:
>
> > Hi everyone,
> >
> > In my quest to get 2x QCN9074 paired and achieving high throughput
> > data transfers, I am now facing issues with the AP configuration.
> >
> > Specifically, I cannot get more than HE-MCS 5 (AP and client 50cm
> > apart) although SNR and RSSI are always very strong and supposedly in
> > specs (SNR > 40db or RSSI < -48db).
> >
> > iw wlp6s0 link
> > Connected to 00:15:61:27:cd:dc (on wlp6s0)
> > SSID: Space
> > freq: 5745
> > RX: 1073584482 bytes (708567 packets)
> > TX: 355824214 bytes (256143 packets)
> > signal: -40 dBm
> > rx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> > tx bitrate: 1729.3 MBit/s 160MHz HE-MCS 4 HE-NSS 4 HE-GI 0 HE-DCM 0
> >
> > In this case iperf3 shows ~950Mbits/s transfer speed. I am hoping to
> > get at least twice as much.
> >
> > It seems to me that either mac80211, ath11k or hostapd are not
> > advertising the available capabilities correctly. I have tried setting
> > hostapd he_basic_mcs_set=65530 or others but did not help.
> >
> > I have added ieee80211_regdom=FR option to cfg80211 module on the AP
> > side. Channel selection is done with ACS survey. I also tried other
> > channels/frequencies without success eg. 5500Mhz.
> >
> > iw reg get
> > global
> > country FR: DFS-ETSI
> > (2400 - 2483 @ 40), (N/A, 20), (N/A)
> > (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
> > (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
> > (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
> > (5725 - 5875 @ 80), (N/A, 13), (N/A)
> > (5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
> > (57000 - 71000 @ 2160), (N/A, 40), (N/A)
> >
> > phy#0 (self-managed)
> > country US: DFS-FCC
> > (2402 - 2472 @ 40), (6, 30), (N/A)
> > (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
> > (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
> > (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
> > (5945 - 7125 @ 160), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW
> >
> > Current setup is:
> > - Intel x86
> > - Ubuntu 22.04
> > - Kernel built from ath 6.4.0-rc6-wt-ath+ (commit:
> > c60d15f389ef9832a8da410e438d81b10327751f)
> > with commit reverted from the bug ticket I opened
> > (https://bugzilla.kernel.org/show_bug.cgi?id=217536).
> > - 1x QCN9074 as AP, 1x as managed client 50cm apart
> > - Both AP and Client are running with the latest 2.7.0 FW.
> >
> > I have started from this ticket
> > (https://bugzilla.kernel.org/show_bug.cgi?id=217286) hostapd config
> > file, and adapted, please find attached.
> >
> > Anyone seeing what could be my issue / how I could debug further ?
>
> As a start please file this to bugzilla as a new bug. Always one issue
> per report, please. Otherwise it's a nightmare to manage the bug
> reports.
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
>
> Try to provide as much as information as you can to the report. You said
> that you have tested it 50 cm apart but have you tested it, for example,
> 3 m apart? Please also include your full kernel .config file and dmesg
> output.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Kalle Valo]

Tanguy Serrat <tanguy@squaremind.io> writes:

> Dear Kalle,
>
> Thank you for your reply.
>
> I have opened two separate issues:
> 1) https://bugzilla.kernel.org/show_bug.cgi?id=217536 - related to a
> previous issue I encountered.
>
> 2) https://bugzilla.kernel.org/show_bug.cgi?id=217652 - related to this feed.
>
> I have tested 3m apart, as described in 217652, results are just
> slightly better in terms of reported MCS. I still seem to be missing
> all capabilities over 7. I have attached the full dmesg log and
> .config file to the bug report

Thanks for filing the report, we will look at bug #217652 and get back
to you. But do note that this will most likely take some time, our
backlog is long and people are also taking vacations. I just came back
yesterday and I'm hoping to take more vacation later this month.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Tanguy Serrat]

> Thanks for filing the report, we will look at bug #217652 and get back
> to you. But do note that this will most likely take some time, our
> backlog is long and people are also taking vacations. I just came back
> yesterday and I'm hoping to take more vacation later this month.

Duly noted, thank you. I hope you and your team will have a good break.

We've spent 150+ hours working on backporting and getting our QCN9074 to work.
We would be extremely grateful if you guys can help us put this
milestone behind, so that we can move forward in the development of
our medical product and be on time for our Radio certification.

Le mar. 11 juil. 2023 à 10:39, Kalle Valo <kvalo@kernel.org> a écrit :
>
> Tanguy Serrat <tanguy@squaremind.io> writes:
>
> > Dear Kalle,
> >
> > Thank you for your reply.
> >
> > I have opened two separate issues:
> > 1) https://bugzilla.kernel.org/show_bug.cgi?id=217536 - related to a
> > previous issue I encountered.
> >
> > 2) https://bugzilla.kernel.org/show_bug.cgi?id=217652 - related to this feed.
> >
> > I have tested 3m apart, as described in 217652, results are just
> > slightly better in terms of reported MCS. I still seem to be missing
> > all capabilities over 7. I have attached the full dmesg log and
> > .config file to the bug report
>
> Thanks for filing the report, we will look at bug #217652 and get back
> to you. But do note that this will most likely take some time, our
> backlog is long and people are also taking vacations. I just came back
> yesterday and I'm hoping to take more vacation later this month.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Tanguy Serrat]

Dear Kalle,

I hope you and your team had great vacations.

Would it be possible to have someone helping us out on our #217652 bug
with QCN9074 ?

This is a strong bottleneck on our side that we really need to solve.

Thank you


Le mer. 12 juil. 2023 à 10:37, Tanguy Serrat <tanguy@squaremind.io> a écrit :
>
> > Thanks for filing the report, we will look at bug #217652 and get back
> > to you. But do note that this will most likely take some time, our
> > backlog is long and people are also taking vacations. I just came back
> > yesterday and I'm hoping to take more vacation later this month.
>
> Duly noted, thank you. I hope you and your team will have a good break.
>
> We've spent 150+ hours working on backporting and getting our QCN9074 to work.
> We would be extremely grateful if you guys can help us put this
> milestone behind, so that we can move forward in the development of
> our medical product and be on time for our Radio certification.
>
> Le mar. 11 juil. 2023 à 10:39, Kalle Valo <kvalo@kernel.org> a écrit :
> >
> > Tanguy Serrat <tanguy@squaremind.io> writes:
> >
> > > Dear Kalle,
> > >
> > > Thank you for your reply.
> > >
> > > I have opened two separate issues:
> > > 1) https://bugzilla.kernel.org/show_bug.cgi?id=217536 - related to a
> > > previous issue I encountered.
> > >
> > > 2) https://bugzilla.kernel.org/show_bug.cgi?id=217652 - related to this feed.
> > >
> > > I have tested 3m apart, as described in 217652, results are just
> > > slightly better in terms of reported MCS. I still seem to be missing
> > > all capabilities over 7. I have attached the full dmesg log and
> > > .config file to the bug report
> >
> > Thanks for filing the report, we will look at bug #217652 and get back
> > to you. But do note that this will most likely take some time, our
> > backlog is long and people are also taking vacations. I just came back
> > yesterday and I'm hoping to take more vacation later this month.
> >
> > --
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: ath11k: QCN9074: low HE-MCS index

[Kalle Valo]

Tanguy Serrat <tanguy@squaremind.io> writes:

> Dear Kalle,
>
> I hope you and your team had great vacations.
>
> Would it be possible to have someone helping us out on our #217652 bug
> with QCN9074 ?
>
> This is a strong bottleneck on our side that we really need to solve.

Unfortunately I haven't been able to look at this at all and not sure
when I'm able to. Can anyone else help?

The bug report is here:

https://bugzilla.kernel.org/show_bug.cgi?id=217652

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k