From: Kalle Valo <kvalo@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: failed to insert STA entry for the AP (error -2)
Date: Fri, 02 Dec 2022 20:46:45 +0200 [thread overview]
Message-ID: <87sfhx3ap6.fsf@kernel.org> (raw)
In-Reply-To: <20221130133016.GC3055@lst.de> (Christoph Hellwig's message of "Wed, 30 Nov 2022 14:30:16 +0100")
Christoph Hellwig <hch@lst.de> writes:
> I'm seeing this fun churn of warns when trying to connect to my AP
> with a brand new Thinkpad T14s Gen3 AMD that I'm trying to install
> Debian on.
>
> The kernel is linux-image-6.0.0-5-amd64 from Debian unstable, which is
> identical to the latest 6.0-stable for ath11k.
>
> [ 280.585881] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem
> 0x98000000-0x981fffff 64bit]
> [ 280.586362] ath11k_pci 0000:01:00.0: MSI vectors: 32
> [ 280.586368] ath11k_pci 0000:01:00.0: wcn6855 hw2.1
> [ 280.741846] mhi mhi0: Requested to power ON
> [ 280.741860] mhi mhi0: Power on setup success
> [ 280.743578] mhi mhi0: firmware: direct-loading firmware
> ath11k/WCN6855/hw2.1/amss.bin
> [ 280.834744] mhi mhi0: Wait for device to enter SBL or Mission mode
> [ 281.468934] ath11k_pci 0000:01:00.0: chip_id 0x12 chip_family 0xb
> board_id 0xff soc_id 0x400c1211
> [ 281.468944] ath11k_pci 0000:01:00.0: fw_version 0x11090c35
> fw_build_timestamp 2022-04-18 20:23 fw_build_id
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
> [ 281.469461] ath11k_pci 0000:01:00.0: firmware: direct-loading
> firmware ath11k/WCN6855/hw2.1/board-2.bin
> [ 281.469544] ath11k_pci 0000:01:00.0: firmware: direct-loading
> firmware ath11k/WCN6855/hw2.1/regdb.bin
> [ 281.479138] ath11k_pci 0000:01:00.0: firmware: direct-loading
> firmware ath11k/WCN6855/hw2.1/board-2.bin
> [ 281.510539] ath11k_pci 0000:01:00.0: firmware: direct-loading
> firmware ath11k/WCN6855/hw2.1/m3.bin
> [ 281.802394] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
> [ 341.715380] wlp1s0: authenticate with 0c:70:4a:89:bc:64
> [ 341.730641] wlp1s0: Invalid HE elem, Disable HE
> [ 341.769475] ath11k_pci 0000:01:00.0: failed to setup rx defrag context
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:
int ath11k_peer_rx_frag_setup(struct ath11k *ar, const u8 *peer_mac, int vdev_id)
{
struct ath11k_base *ab = ar->ab;
struct crypto_shash *tfm;
struct ath11k_peer *peer;
struct dp_rx_tid *rx_tid;
int i;
tfm = crypto_alloc_shash("michael_mic", 0, 0);
if (IS_ERR(tfm))
return PTR_ERR(tfm);
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).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-12-02 18:47 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 [this message]
2022-12-03 15:52 ` Christoph Hellwig
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=87sfhx3ap6.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=hch@lst.de \
--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).