From: Benjamin Eggerstedt <benjamin.eggerstedt@gmail.com>
To: Lingbo Kong <lingbo.kong@oss.qualcomm.com>
Cc: "ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Subject: Re: wifi: ath12k: Attempting MLO with main (6.15.rc7) for NCM865 / WCN7850 in station mode leads to crash/backtrace
Date: Tue, 24 Jun 2025 22:24:25 +0200 [thread overview]
Message-ID: <F8842C33-E474-40F1-8E47-CD1CDF9782BF@gmail.com> (raw)
In-Reply-To: <81d2794c-ac3f-4917-9267-af91afd4baa2@oss.qualcomm.com>
Dear Lingbo & team,
> > Should I see EMLSR support?
> > I noticed that “iw” output no longer has a TX nor RX Rate:
Indeed I can see the TX and RX rate again with the patches you kindly suggested.
The signal at -128 dBm would still be incorrect.
I still cannot see support for EMLSR, although the corresponding patches are part of v6.16.rc1 (ath-current-20250617)
debadm@debian:~$ sudo iw dev wlp3s0 station dump Station
Station 88:3c:93:01:ce:40 (on wlp3s0)
inactive time: 22360 ms
rx bytes: 2533534
rx packets: 9680
tx bytes: 4459
tx packets: 37
tx retries: 0
tx failed: 0
beacon loss: 0
beacon rx: 0
rx drop misc: 15
signal: -128 dBm
signal avg: 0 dBm
beacon signal avg: 0 dBm
tx bitrate: 1441.1 MBit/s 80MHz EHT-MCS 13 EHT-NSS 2 EHT-GI 0
tx duration: 0 us
rx bitrate: 960.7 MBit/s 80MHz EHT-MCS 9 EHT-NSS 2 EHT-GI 0
rx duration: 0 us
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 0
beacon interval:0
connected time: 505 seconds
associated at [boottime]: 161.391s
associated at: 1750795842112 ms
current time: 1750796347204 ms
Corresponding output from AP side (5 GHz in this association).
Please note how EMLSR is still being reported as “No”.
==== STA Info From Link: ath101 =======
ADDR AID CHAN TXRATE RXRATE RSSI MINRSSI MAXRSSI IDLE TXSEQ RXSEQ CAPS XCAPS ACAPS ERP STATE MAXRATE(DOT11) HTCAPS VHTCAPS ASSOCTIME IEs MODE RXNSS TXNSS PSMODE
b6:b9:b8:5a:a2:05 4 100 960M 1441M -29 -36 -22 11 0 65535 P EWBQ NULL 0 b 1441200 AWRSM 1gGTRs 00:08:15 RSN WME IEEE80211_MODE_11BEA_EHT80 2 2 0
RSSI is combined over chains in dBm
Minimum Tx Power : 0
Maximum Tx Power : 30
HT Capability : Yes
VHT Capability : Yes
MU capable : Yes
SNR : 66
Operating band : 5GHz
Current Operating class : 128
Supported Operating classes : 81 83 84 115 116 117 118 119 120 121 122 123 124 125 126 127 128 131 132 133 134 137 130 128 135 133
Supported Rates(Mbps) : 6 9 12 18 24 36 48 54
Max STA phymode : IEEE80211_MODE_11BEA_EHT80
MLO : Yes
MLD Addr : 50:cf:14:8e:e3:d1
Num Partner links : 2
Partner link 0: ADDR :f2:0a:ab:8a:78:12, Link ID: 0 Bridge link: 0
Partner link 1: ADDR :da:8a:5e:b9:f8:69, Link ID: 2 Bridge link: 0
EMLSR capable : No
EMLMR capable : No
STR capable : Yes
Thanks,
Regards,
Benny
next prev parent reply other threads:[~2025-06-24 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 5:56 wifi: ath12k: Attempting MLO with main (6.15.rc7) for NCM865 / WCN7850 in station mode leads to crash/backtrace Lingbo Kong
2025-06-24 20:24 ` Benjamin Eggerstedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 10:32 Benjamin Eggerstedt
2025-06-01 19:52 ` Benjamin Eggerstedt
2025-06-03 3:01 ` Baochen Qiang
2025-06-03 7:39 ` Baochen Qiang
2025-06-09 15:56 ` Benjamin Eggerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F8842C33-E474-40F1-8E47-CD1CDF9782BF@gmail.com \
--to=benjamin.eggerstedt@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=lingbo.kong@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.