From patchwork Tue Dec 28 00:59:09 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Kevin Anderson X-Patchwork-Id: 529103 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8D390C433EF for ; Tue, 28 Dec 2021 00:59:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234273AbhL1A7X (ORCPT ); Mon, 27 Dec 2021 19:59:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49120 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234271AbhL1A7X (ORCPT ); Mon, 27 Dec 2021 19:59:23 -0500 Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A77A1C06173E for ; Mon, 27 Dec 2021 16:59:22 -0800 (PST) Received: by mail-ua1-x92c.google.com with SMTP id r15so29523659uao.3 for ; Mon, 27 Dec 2021 16:59:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=/bFuADBwC4EPW7y3RrPU0rN87a72JnY9KmW5k5Yc2XY=; b=iRixyO4gLoSd1Pxr/PPmw/sEvf8snM3x8qhP2cAMIb/h0/FoKKsyK5+p6tHfRe7TnO PkWiZwaijlseZ9cnqmPqK15WsmQcxzuJ6v1rPV0yviTMIYsZGsWyMcfYCeh4XTvF7+S/ ZqwBFuxmuPiWIo3MspiNPb9alo9dXWjvoWJNs8KP58sF6sroX+3YwRcdk23+WKL44tMW Xflz0EqKGC58JA4t56RYHMhZoPQ7lSNkDbCxFa53Qu4IhghucKjQRQjQLX3M0x+L0tjV fCVXmjhx5BLho6fgwg/0lyMaCYplvTR2OGL/VARzjItGQ4rizb0uEVrriPhFDi1k/Tz6 qzzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/bFuADBwC4EPW7y3RrPU0rN87a72JnY9KmW5k5Yc2XY=; b=OnME9Qjn1vu/4t5zkOrqbrlgZx1k0fIQdqm/tex5K+h7auQ3r7XyDVnYAywOZq7cGl BiZIouHFoEyrVu1fG5kvPcq456tXyEUKYjEXLEe73wLr0FEl0oR9H/r4iGSYDbn2COxk hSLNT1+ytIkKgng9t938E0nmZz0McTIpvGoGJTDJ8uWYCsp3QNOulAPDRLdyRasdaiu6 bwrwcVyGoWhLHqX5dpkrWsd+wFweJiII7uuD6DvS8TKIExa1q5Kr3uGv4AQgln4disD8 tfrQNCeWkaZE7rmrlGwIND/Dsn9I2CeoYCjzZ5C4e3vIsBIewREsrFDNa4j1QnadFHx3 Mt+A== X-Gm-Message-State: AOAM533yES8SX6gekCJvjiMqaHEQAh+BZfZ4Hnaz+ze4WtJLBbLJCttP cf6epxYYiW2VwanfEuotRAwnVW99yJTF7ZPchOU= X-Google-Smtp-Source: ABdhPJwpVo/O6Wu3KoFmM+ZXkrYxHvGo/zbQNRHtqdmTLiyKT0jCiuNRvaV3iONTlUg6dvc0/UxpAtF4fT3svu+nVkI= X-Received: by 2002:a05:6102:31ad:: with SMTP id d13mr5236347vsh.55.1640653160694; Mon, 27 Dec 2021 16:59:20 -0800 (PST) MIME-Version: 1.0 From: Kevin Anderson Date: Mon, 27 Dec 2021 19:59:09 -0500 Message-ID: Subject: iwlwifi Backport Request To: gregkh@linuxfoundation.org, luciano.coelho@intel.com, johannes@sipsolutions.net, stable@vger.kernel.org, ilan.peer@intel.com, johannes.berg@intel.com Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org Hello, I wanted to see if I could have two patches backported to 5.15 stable that concern Intel iwlwifi AX2XX stability. The patches are attached to the kernel bugzilla that can be found here: https://bugzilla.kernel.org/show_bug.cgi?id=214549. I've also attached them to this email. The patches fix an issue with the Intel AX210 that I have where it can cause a firmware reset when the device is under load causing performance to drop to around ~500Kb/s till the interface is restarted. This reset is easy to reproduce during normal use such as streaming videos and is problematic for devices such as laptops that primarily use wifi for connectivity. The mac80211 change is currently in the 5.16 RC and the scan timeout is in netdev-next and is supposed to be scheduled for 5.17 from what I can tell. I believe that the patches meet the requirements of the -stable tree as it makes the adapter for many users including myself difficult to use reliably. If this is the incorrect venue for this please let me know. Thanks, Kevin Anderson >From fa9f057b7ba73e9da0dbd0abf2b0266742471e9c Mon Sep 17 00:00:00 2001 From: Ilan Peer Date: Mon, 29 Nov 2021 11:13:31 +0200 Subject: [PATCH] iwlwifi: mvm: Increase the scan timeout guard to 30 seconds With the introduction of 6GHz channels the scan guard timeout should be adjusted to account for the following extreme case: - All 6GHz channels are scanned passively: 58 channels. - The scan is fragmented with the following parameters: 3 fragments, 95 TUs suspend time, 44 TUs maximal out of channel time. The above would result with scan time of more than 24 seconds. Thus, set the timeout to 30 seconds. type=bugfix ticket=jira:WIFI-157075 fixes=unknown Change-Id: I346fa2e1d79220a6770496e773c6f87a2ad9e6c4 Signed-off-by: Ilan Peer --- drivers/net/wireless/intel/iwlwifi/mvm/scan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/scan.c b/drivers/net/wireless/intel/iwlwifi/mvm/scan.c index ee3aff8bf7c2..3853222911d9 100644 --- a/drivers/net/wireless/intel/iwlwifi/mvm/scan.c +++ b/drivers/net/wireless/intel/iwlwifi/mvm/scan.c @@ -2478,7 +2478,7 @@ static int iwl_mvm_check_running_scans(struct iwl_mvm *mvm, int type) return -EIO; } -#define SCAN_TIMEOUT 20000 +#define SCAN_TIMEOUT 30000 void iwl_mvm_scan_timeout_wk(struct work_struct *work) { -- 2.17.1