Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp578089ybl; Wed, 21 Aug 2019 02:12:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrWJCJy+7pKHuj7dlYvqkjR12qS26tDmXQrvdwfnyPsZ2hwsaRxPY8wo7Y+sGdD/kC3dav X-Received: by 2002:a17:902:b588:: with SMTP id a8mr20903219pls.15.1566378749355; Wed, 21 Aug 2019 02:12:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566378749; cv=none; d=google.com; s=arc-20160816; b=sn7YhYKdIczuGFNtVCPfrBneRhZX2rLOzoCAnp6u0neNmFYXsKacGNyPXxbFagYhSk lH+1EeVb/k3NFkRWfw8yZbI1tazgknNYnU4h0mwanq6zTlMkS9n1azWMAt0I3i4jE5b5 btSNeNQLr6a9wIAPZ5BRSyaKKt7NbDviHg27ht/mVfy7DsyEHeyddGRzSXgZxlvIM//U SBUWRkFt0qfUEadOzgpTb3X/rrunxde3hNuxn5RKEd3u4h0Y34cRU8fnjfyHHq9kKvTu URDVunOtQKNSV+5lKrLGewF0TKRg184D/lEW1vGv3KR1KzQAJPES5Th0ZyosaTpC2ICB ZVng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=/M4rQlzBwevUlzcXzdgWRG9LsOfP2ZtjXyd7C068O5U=; b=BerUNve8S50iixrVA9p0O7btugimuItvseZxealkcr9Ahqp0Zwf1vnvyQpON7cjpXk bzWi45GxgyeaoH/UY1nYJ7GKv2tORpHRDMXPLeTekK95pzhLK7Paa/3KhQByHQg47odi TSWO//KMB1hXRp4Pl5pX2ZbRa/fpxBd6Shk8dyqcmSm7V5kNOo5RZHtVTIKj1JaCuupV tV/+K9tNn2kBfXmQX+EHR5Ks8wIb3Ckd1VwR9hfWzDZCjL3R1KVMWzplinjN56vjDLVp WCXtjeiG9E811m1H7rPXWFeUwt6w/1HU3wnL2qAGHV2kbZunwdssH1Ayc1R+bKux0yh6 gjIQ== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l6si13984352pgp.391.2019.08.21.02.12.01; Wed, 21 Aug 2019 02:12:29 -0700 (PDT) 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727291AbfHUIr3 (ORCPT + 99 others); Wed, 21 Aug 2019 04:47:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42506 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726715AbfHUIr3 (ORCPT ); Wed, 21 Aug 2019 04:47:29 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id ECD5C308212A; Wed, 21 Aug 2019 08:47:28 +0000 (UTC) Received: from localhost (ovpn-204-173.brq.redhat.com [10.40.204.173]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2310F5D9E1; Wed, 21 Aug 2019 08:47:25 +0000 (UTC) Date: Wed, 21 Aug 2019 10:47:24 +0200 From: Stanislaw Gruszka To: Felix Fietkau Cc: Lorenzo Bianconi , linux-wireless , Ryder Lee , Roy Luo Subject: Re: [PATCH 5.3] mt76: mt76x0e: don't use hw encryption for MT7630E Message-ID: <20190821084724.GB20223@redhat.com> References: <1565703400-10623-1-git-send-email-sgruszka@redhat.com> <20190815100936.GA21775@redhat.com> <727fd528-16c1-e3b3-e1a9-2edbcbdddee7@nbd.name> <20190819110639.GA6037@redhat.com> <7b46ab63-d69d-f389-b3c2-245cbe11c7b7@nbd.name> <20190820112438.GA2227@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190820112438.GA2227@redhat.com> User-Agent: Mutt/1.11.3 (2019-02-01) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.42]); Wed, 21 Aug 2019 08:47:29 +0000 (UTC) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, Aug 20, 2019 at 01:24:39PM +0200, Stanislaw Gruszka wrote: > > Can you test if disabling hw encryption only for shared or only for > > pairwise keys makes any difference? > > Disabling only pairwise keys helps. Disabling only shared keys does > not help. > > Not sure if this will be helpful information or make things more > confusing, but seems the difference between mt76_txq_schedule() > and tasklet_schedule() in mt76_wake_tx_queue() is that on > mt76_txq_schedule() some tx packets are serialized by dev->rx_lock > (because some ARP and TCP packets are sent via network stack as response > of incoming packet within ieee80211_rx_napi() call). Removing > spin_lock(&dev->rx_lock) in mt76_rx_complete() make the problem > reproducible again with mt76_txq_schedule() & HW encryption. So, I think this is FW/HW issue related with encryption and ordering and we should apply patch originally posted in this thread that disable HW encryption for MT7630E. I do not think we should disable HW encryption only for pairwise keys, because FW/HW can have the same bug for shared keys, but is not triggered in my test, as we do not sent lot of group frames. Stanislaw