Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp3643160rwb; Sat, 3 Dec 2022 08:10:53 -0800 (PST) X-Google-Smtp-Source: AA0mqf4w/SK6qdpZbUJ7cM0ndfZwXChRJISWeqQlUzTnfOb+BINfDQ0kPHFuu8TGcGGS2XgstBNO X-Received: by 2002:a05:6402:114c:b0:457:35d4:ac66 with SMTP id g12-20020a056402114c00b0045735d4ac66mr9810569edw.415.1670083853434; Sat, 03 Dec 2022 08:10:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670083853; cv=none; d=google.com; s=arc-20160816; b=ecQaKIEG4B22M9eoUQLpbv4sKYgCw89zMsqK3zoiyK3UPw+7LpXnU4sSwEoCs1wjF9 3SEpgUbq0Uu3S9lDosUehsEj+nfBUNolQEdDNp3Kw0PjlYfLXiW40LIpiAdXpK3Aymv5 PoenkW4rYBWa40qX4O3tVg9npM8BYB3YQMnW4kPVlBZl75TlCoI53spZjwW0cVCb3Zt9 gvhC3NOyVWIkf8yTKHUKBKPVTteB9zaaB6ZeqldYOiC2np39h9vqRl9fsJU1VFJQCe0H pNYdNqqtKBFMap8Bs4LMRXHXLRqxC7smkBktxfle4X02/+VT0taREjRgHzxLwG/OWlbi ijpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=wH3o5FoqYf/0Oo5+nXlEZ+tkun9vJcCsXMiqlO//Rz0=; b=MfO4h6j6HkLpXf2vhzZu2scPPRam4iqMp/wvNGhP9w3D1On0U5gVzYrshrzYCHDq0B DrA4Za0fgpronEYHCS/mGZ+Iu2x/rSqMcwxKo57dkoJghbyjdrFrtGUoBMOPV5v/A+Su AGay10c+gJXKEJKQhd/pIhx/Ep0oeNl5vWLLf5FrFInwZ38EG6V0TS3JM2Suq2iB4XkH sXPObbfRec1b3L/JoqTxPmX5RycfMVsT9mVFZxQMpv0bQF/DR2Q6YEC5V77BRTFQV53h H4sf6OTbgkaEw8Y+ZN1OFzD5ZoRpL3IyG/cOvwgzBNXxrTMIF3emNk8hFHWxo2VTHAW1 2TaA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j11-20020a05640211cb00b0046adf195723si9013113edw.251.2022.12.03.08.10.33; Sat, 03 Dec 2022 08:10:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229670AbiLCPwk (ORCPT + 66 others); Sat, 3 Dec 2022 10:52:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39972 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229631AbiLCPwj (ORCPT ); Sat, 3 Dec 2022 10:52:39 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2527CB1C6 for ; Sat, 3 Dec 2022 07:52:32 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 3E1E468AFE; Sat, 3 Dec 2022 16:52:28 +0100 (CET) Date: Sat, 3 Dec 2022 16:52:27 +0100 From: Christoph Hellwig To: Kalle Valo Cc: Christoph Hellwig , ath11k@lists.infradead.org, linux-wireless@vger.kernel.org Subject: Re: failed to insert STA entry for the AP (error -2) Message-ID: <20221203155227.GA13254@lst.de> References: <20221130122807.GA31720@lst.de> <87o7so4nr2.fsf@kernel.org> <20221130125236.GA865@lst.de> <87k03c4mdb.fsf@kernel.org> <20221130133016.GC3055@lst.de> <87sfhx3ap6.fsf@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sfhx3ap6.fsf@kernel.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.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.