mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Kalle Valo <kvalo@kernel.org>
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, 4 Sep 2024 23:42:35 +0200	[thread overview]
Message-ID: <00dfdaab-4d26-45f6-b69d-049ae489b2bd@molgen.mpg.de> (raw)
In-Reply-To: <87bk13jwzv.fsf@kernel.org>

Dear Kalle,


Thank you for your reply.


Am 04.09.24 um 16:48 schrieb Kalle Valo:
> Paul Menzel writes:

>> 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).
>>
>> 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?

As an ignorant user, I do not know what to do with the warning. I’d like 
to see a suggestion how to get rid of the warning. Maybe:

     wlp58s0: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware 
in X s (-110), please report it to the vendor firmware


Kind regards,

Paul

  reply	other threads:[~2024-09-04 21:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 10:45 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
2024-09-04 21:42   ` Paul Menzel [this message]
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=00dfdaab-4d26-45f6-b69d-049ae489b2bd@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®