> -----Original Message-----
> From: Zenm Chen <zenmchen@xxxxxxxxx>
> Sent: Friday, January 12, 2024 12:36 AM
> To: martin.kaistra@xxxxxxxxxxxxx
> Cc: Jes.Sorensen@xxxxxxxxx; bigeasy@xxxxxxxxxxxxx; kvalo@xxxxxxxxxx; linux-wireless@xxxxxxxxxxxxxxx;
> Ping-Ke Shih <pkshih@xxxxxxxxxxx>; rtl8821cerfe2@xxxxxxxxx
> Subject: [PATCH v3 21/21] wifi: rtl8xxxu: declare concurrent mode support for 8188f
>
> Hi,
>
> The rtl8xxxu driver can't establish the connection after applying this series
> of the patches. Please help me, thanks!
>
> OS: Arch Linux (kernel version: 6.6.10-arch1-1)
> devices tested: MERCUSYS MW300UM (RTL8192EU)
> MERCURY MW310UH (RTL8192FU)
>
[...]
> [ 186.081741] wlp0s18f2u4: associated
> [ 186.218451] wlp0s18f2u4: Limiting TX power to 30 (30 - 0) dBm as advertised by bc:e6:3f:5f:9c:cd
> [ 195.553755] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7
> hardware; use nl80211
> [ 231.035382] wlp0s18f2u4: deauthenticating from bc:e6:3f:5f:9c:cd by local choice (Reason:
> 3=DEAUTH_LEAVING)
Locally trying to disconnect after 30 seconds. Can you try non-secure
connection and specify static IP to see if it can work?
I reviewed the patchset again, no obvious change if you are using a vif with
station mode only. The only one I'm not very sure is a commit related to
security CAM:
Fixes: b837f78fbffa ("wifi: rtl8xxxu: add hw crypto support for AP mode")
Since each patch can be seen as individual one, could you help to bisect
the cause?
Ping-Ke
