[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8eda1bd2-88fc-4262-aec0-6f88a73797ef@molgen.mpg.de>
Date: Fri, 11 Oct 2024 14:48:44 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: James Prestwood <prestwoj@...il.com>
Cc: Kalle Valo <kvalo@...nel.org>, Baochen Qiang <quic_bqiang@...cinc.com>,
linux-wireless@...r.kernel.org, ath10k@...ts.infradead.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110)
(ETIMEDOUT)
Dear James,
Am 04.09.24 um 16:09 schrieb James Prestwood:
> On 9/4/24 3:45 AM, Paul Menzel wrote:
>> Linux 6.11-rc6+ logged the warning below when resuming from ACPI S3
>> (or unloading and loading the `ath10k_core`/`ath10k_pci` modules)
>> having been connected to an AVM network:
>>
>> wlp58s0: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110)
>>
>> Error code 110 is the value for ETIMEDOUT. I saw James patch [1], and
>> applied it, and the error is still there (as expected).
>
> My patch won't actually fix the timeout, I just lowered the time that
> ath10k would wait before it continued which fixed some incompatibility
> on the AP side of things. Based on your logs though, it appears you
> already got disconnected before the failure to remove the key...
I am still applying your patch manually on the current master branch,
and it looks like it hasn’t still been reviewed. Maybe it’s due to the
RFC tag. Do you plan on moving it ahead?
Kind regards,
Paul
>> [1]: https://lore.kernel.org/all/20240814164507.996303-1-prestwoj@gmail.com/
Powered by blists - more mailing lists