Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1884407ybc; Wed, 20 Nov 2019 05:42:43 -0800 (PST) X-Google-Smtp-Source: APXvYqxQpXlqTov8ux9Igz/jaE330b4ofXhBYcgn+28A09yQx/jG/t3oVqZyCODRftBuEFwelLkj X-Received: by 2002:adf:ba4f:: with SMTP id t15mr3241520wrg.24.1574257363232; Wed, 20 Nov 2019 05:42:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574257363; cv=none; d=google.com; s=arc-20160816; b=wrjymNAEvJzufww8xq0ZVzl1gv8Ii0kB79T+E3KgrigHnfZOF1V5resigW3DPKnno3 Oj6+8YgzU3DmjgjDwM0eDkwKTAKVo/ydK9vy6ODFAwanJYECt/o4VCjTq+PMClmsO93s gyjL9bomtsN5TaKrmgsTQ4YPd49TVgEnL1mjn9XehI1XdLAomMgcazhXwtcULUuZvyQV UqaNLfllO5Oh11zJDz57e8uEqAa3HtGlDOfnJQZlU+v2IllgJ1V1y3J2dCadhiKa8pvB /V/leHyTAanXqSZGyAiZFQ5jup3usxzfT3d8Fq2QCUEftySSJCWOOXGHgnwunt16/JuU KBSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=2mI8BzD9K1HKmqy0MIq6J8nNdrLamnyyiCiA3H07JMY=; b=sLBFG5yFu1B1OP9JE3jNWugXbfe5vWrwwCTW+GUEwOlg+f5CvrjEM4gQci16eV33mK 7iOL+UqlwhXrO2YtxgYZriXzWEwYDI4wElYdS1hawBvTpiynhryKV89N48jp5tp5C29d 0qSfAyngSebK0lpoh2/tYUd7KSNbTxZfwR6aFycfEwPwd00oAouJne3rJGrkxDOj1Mck WKsv18yDHgayYUOr9NNLf4PCGU1eFmwjt3FKmW2/p2OLU7y2x68oPwlZdjXW0GSvga9i oLek3D7etBsT5Q7u571981Jbk1vYuw1IdRVDns4GXuEV5zJePPPGb0MFhMBRdL77X3JQ KNSQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c36si18156244edb.58.2019.11.20.05.42.17; Wed, 20 Nov 2019 05:42:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729475AbfKTN0i (ORCPT + 99 others); Wed, 20 Nov 2019 08:26:38 -0500 Received: from mga07.intel.com ([134.134.136.100]:43274 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729457AbfKTN0i (ORCPT ); Wed, 20 Nov 2019 08:26:38 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Nov 2019 05:26:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,222,1571727600"; d="scan'208";a="218627112" Received: from egrumbac-mobl1.jer.intel.com ([10.12.117.10]) by orsmga002.jf.intel.com with ESMTP; 20 Nov 2019 05:26:35 -0800 From: Emmanuel Grumbach To: linux-wireless@vger.kernel.org Cc: luciano.coelho@intel.com, Emmanuel Grumbach , stable@vger.kernel.org Subject: [PATCH] iwlwifi: mvm: don't send the IWL_MVM_RXQ_NSSN_SYNC notif to Rx queues Date: Wed, 20 Nov 2019 15:26:28 +0200 Message-Id: <20191120132628.30731-1-emmanuel.grumbach@intel.com> X-Mailer: git-send-email 2.17.1 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org The purpose of this was to keep all the queues updated with the Rx sequence numbers because unlikely yet possible situations where queues can't understand if a specific packet needs to be dropped or not. Unfortunately, it was reported that this caused issues in our DMA engine. We don't fully understand how this is related, but this is being currently debugged. For now, just don't send this notification to the Rx queues. This de-facto reverts my commit 3c514bf831ac12356b695ff054bef641b9e99593: iwlwifi: mvm: add a loose synchronization of the NSSN across Rx queues This issue was reported here: https://bugzilla.kernel.org/show_bug.cgi?id=204873 https://bugzilla.kernel.org/show_bug.cgi?id=205001 and others maybe. Fixes: 3c514bf831ac ("iwlwifi: mvm: add a loose synchronization of the NSSN across Rx queues") CC: # 5.3+ Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c b/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c index 75a7af5ad7b2..8925fe5976cb 100644 --- a/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c +++ b/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c @@ -521,7 +521,11 @@ static void iwl_mvm_sync_nssn(struct iwl_mvm *mvm, u8 baid, u16 nssn) .nssn_sync.nssn = nssn, }; - iwl_mvm_sync_rx_queues_internal(mvm, (void *)¬if, sizeof(notif)); + /* + * This allow to synchronize the queues, but it has been reported + * to cause FH issues. Don't send the notification for now. + * iwl_mvm_sync_rx_queues_internal(mvm, (void *)¬if, sizeof(notif)); + */ } #define RX_REORDER_BUF_TIMEOUT_MQ (HZ / 10) -- 2.17.1