From: Kalle Valo <kvalo@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
James Prestwood <prestwoj@gmail.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110) (ETIMEDOUT)
Date: Wed, 04 Sep 2024 17:48:20 +0300 [thread overview]
Message-ID: <87bk13jwzv.fsf@kernel.org> (raw)
In-Reply-To: <d8253ab3-f4f0-40fd-a550-d75eef121b56@molgen.mpg.de> (Paul Menzel's message of "Wed, 4 Sep 2024 12:45:01 +0200")
Paul Menzel <pmenzel@molgen.mpg.de> writes:
> Dear Linux folks,
>
>
> 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 exepected).
>
> Can the warning be improved so the user know, which component is at fault?
The warning comes from mac80211 and it already contains your network
interface name (wlp58s0). What else would you want to see?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
next prev parent reply other threads:[~2024-09-04 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:45 failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110) (ETIMEDOUT) Paul Menzel
2024-09-04 10:49 ` Baochen Qiang
2024-09-04 14:09 ` James Prestwood
2024-10-11 12:48 ` Paul Menzel
2024-10-11 16:36 ` James Prestwood
2024-09-04 14:48 ` Kalle Valo [this message]
2024-09-04 21:42 ` Paul Menzel
2024-09-05 13:23 ` Kalle Valo
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=87bk13jwzv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=prestwoj@gmail.com \
--cc=quic_bqiang@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox