Re: ath10k_pci: disassociated from x:y:z:a (Reason: 23=IEEE8021X_FAILED)

[James Prestwood <prestwoj@gmail.com>]

Hi Paul,

On 6/24/24 8:59 AM, Paul Menzel wrote:
> Dear Linux folks,
>
>
> On the Dell XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022 with
>
>     3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 
> 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
>
> I got a connection drop in the eduroam network at the Marburg 
> University, and Linux 6.10-rc5 logged:
>
>     [ 5436.658691] wlp58s0: Limiting TX power to 2 dBm as advertised 
> by 08:ec:f5:dc:f1:ef
>     [ 7240.208199] wlp58s0: disassociated from 08:ec:f5:dc:f1:ef 
> (Reason: 23=IEEE8021X_FAILED)
>     [ 7243.279668] ath10k_pci 0000:3a:00.0: failed to install key for 
> vdev 0 peer 08:ec:f5:dc:f1:ef: -110
>     [ 7243.279683] wlp58s0: failed to remove key (0, 
> 08:ec:f5:dc:f1:ef) from hardware (-110)
>     [ 7258.176009] wlp58s0: authenticate with 08:ec:f5:dc:f0:0f (local 
> address=9c:b6:d0:d1:6a:b1)
>     [ 7258.176024] wlp58s0: send auth to 08:ec:f5:dc:f0:0f (try 1/3)
>     [ 7258.177072] wlp58s0: authenticated
>
> Please find the output of `dmesg` attached.

FWIW I don't have a solution but we see this routinely, mainly on 
roaming when the old key is being removed for the prior BSS. I looked at 
the driver code as best I could and it appeared that the error on 
removal shouldn't cause any issues. When the new key is added it is 
successful (otherwise we'd see a separate error), and at least in my 
devices the connection to the new BSS succeeds.

Thanks,

James

>
>
> Kind regards,
>
> Paul