From: Christoph Hellwig <hch@lst.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: failed to insert STA entry for the AP (error -2)
Date: Sat, 3 Dec 2022 16:52:27 +0100 [thread overview]
Message-ID: <20221203155227.GA13254@lst.de> (raw)
In-Reply-To: <87sfhx3ap6.fsf@kernel.org>
On Fri, Dec 02, 2022 at 08:46:45PM +0200, Kalle Valo wrote:
> Haven't seen this before either. Really unfortunate that the warning
> message message is not printing the error value (missed that during
> review), but I suspect the error is coming from crypto_alloc_shash()
> call:
> Any chance you could check that? Also please check that
> CONFIG_CRYPTO_MICHAEL_MIC is enabled (it should be as CONFIG_ATH11K
> depends on it).
So, this is the debian-installer case onc again. CONFIG_CRYPTO_MICHAEL_MIC
is enabled in the kernel config, but michael_mic.ko is not present on
the installation media. Once I side-load it, the problem goes away.
I guess I'll respind the MODULE_SOFTDEP patch to include michael_mic,
but if you have a good idea to make the error reporting more useful that
would be appreciated as well.
next prev parent reply other threads:[~2022-12-03 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221130122807.GA31720@lst.de>
[not found] ` <87o7so4nr2.fsf@kernel.org>
[not found] ` <20221130125236.GA865@lst.de>
2022-11-30 13:12 ` ath11k vs ar_qrtr? Kalle Valo
2022-11-30 13:22 ` Christoph Hellwig
2022-11-30 17:18 ` Kalle Valo
2022-11-30 13:30 ` failed to insert STA entry for the AP (error -2) Christoph Hellwig
2022-12-02 18:46 ` Kalle Valo
2022-12-03 15:52 ` Christoph Hellwig [this message]
2022-12-07 12:49 ` Kalle Valo
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 14:24 ` Cyril Brulebois
2022-12-08 18:44 ` 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=20221203155227.GA13254@lst.de \
--to=hch@lst.de \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).