Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp149087imd; Wed, 31 Oct 2018 16:17:57 -0700 (PDT) X-Google-Smtp-Source: AJdET5eIbw/1PdfKtyNi5fDeKIoZoKQpKiw0UhkiQccjSy/mDXF77ElYk13s/ty3i7eG/NPWlhKp X-Received: by 2002:a17:902:8f8f:: with SMTP id z15-v6mr5280497plo.257.1541027877922; Wed, 31 Oct 2018 16:17:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541027877; cv=none; d=google.com; s=arc-20160816; b=PmKhKwy8fDPfAhbjzqdQpCpCEojMbtI8FCB37lUUvHauFSZ4/8Hd1r10FjEkwi1u5G bSmT7jCVYsv3CCYBnzPTbOjKaca1QzPh2FreZIVViWP8I0UonBmns7QxNV0NreljUpqj tXIDIoXuDQxni83DsrCAwdCwZ1t2jjPSHu/0BEJlZq999DlmcFAS//50IDdieOfJ9gZW u7jbJ2PXywJCn8/GbO0D7JjOrlSOrfnJO8YTgAVBvsuuTv9vc897ACV7OqgepK4IsVsE 89GkincTWZjXMYyxZLGeiGOtGGmKI3CCwXtBLCmsSLOtZZMF9OJnUg88VS9veOvw3EWs ymaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature; bh=bip2DZKniqkPGDlY+7iqWsw4OQVcMbluWeTmbUxzr00=; b=WBXch6AbPSUY1HA+J9QykSejU/ejCmqYVQ7ch45PnltQ4cD24n6vz+SI9Wi3b9sTbu fBn/rYGozVFWYDOno6kRwOMfNeUhDkVv8nRPytfKkcrjzu7xQpUsKA+neBJ96/EW24pm HPYf3UXGBO/0x2TebNNaemAqA6g/7jV/P1xvhI/UJrwX5dIc+f5ceyHO0mo3kX31AIRW EskHt0Yhrr+SI1rlbn0kE3tvMTNYBJKBEQLsmaSeSp1GmBrEV70k13ctm43fbYC5ApV5 pKtxm67rh2iPd/T7lDG4OGzP78vGtAAuZOEXMibVdm1PiEIXiwbiR7ydZz+/1i2ux9wl Urjw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=axuQZaLg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 62-v6si13096790ply.423.2018.10.31.16.17.43; Wed, 31 Oct 2018 16:17:57 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=axuQZaLg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732086AbeKAIMJ (ORCPT + 99 others); Thu, 1 Nov 2018 04:12:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:36636 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732006AbeKAIMH (ORCPT ); Thu, 1 Nov 2018 04:12:07 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A074920866; Wed, 31 Oct 2018 23:11:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541027515; bh=U2b9FP75za6tzP3O9lXlsZ1LxB3AwXLB4xKrYLoi70U=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=axuQZaLgcDs9TVjW7E/UOO/EtCwhFacHAWK8xgXIpPzQwXWVYJT2SKJ5Dl7CRYedF vJ9co9JnzlhAejjnWawIj0xtlXBULf+rCa15xHB0RIseiXjpkpqMsygWeKYvkiLMMe p4a+AcmgT3dHxO54NB9KqcH0cZirkxBqG8UVjwvo= From: Sasha Levin To: stable@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Martin Willi , Kalle Valo , Sasha Levin Subject: [PATCH AUTOSEL 4.4 19/32] ath10k: schedule hardware restart if WMI command times out Date: Wed, 31 Oct 2018 19:11:24 -0400 Message-Id: <20181031231137.29429-19-sashal@kernel.org> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181031231137.29429-1-sashal@kernel.org> References: <20181031231137.29429-1-sashal@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Martin Willi [ Upstream commit a9911937e7d332761e8c4fcbc7ba0426bdc3956f ] When running in AP mode, ath10k sometimes suffers from TX credit starvation. The issue is hard to reproduce and shows up once in a few days, but has been repeatedly seen with QCA9882 and a large range of firmwares, including 10.2.4.70.67. Once the module is in this state, TX credits are never replenished, which results in "SWBA overrun" errors, as no beacons can be sent. Even worse, WMI commands run in a timeout while holding the conf mutex for three seconds each, making any further operations slow and the whole system unresponsive. The firmware/driver never recovers from that state automatically, and triggering TX flush or warm restarts won't work over WMI. So issue a hardware restart if a WMI command times out due to missing TX credits. This implies a connectivity outage of about 1.4s in AP mode, but brings back the interface and the whole system to a usable state. WMI command timeouts have not been seen in absent of this specific issue, so taking such drastic actions seems legitimate. Signed-off-by: Martin Willi Signed-off-by: Kalle Valo Signed-off-by: Sasha Levin --- drivers/net/wireless/ath/ath10k/wmi.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c index 5bb1be478954..f201e50447d8 100644 --- a/drivers/net/wireless/ath/ath10k/wmi.c +++ b/drivers/net/wireless/ath/ath10k/wmi.c @@ -1749,6 +1749,12 @@ int ath10k_wmi_cmd_send(struct ath10k *ar, struct sk_buff *skb, u32 cmd_id) if (ret) dev_kfree_skb_any(skb); + if (ret == -EAGAIN) { + ath10k_warn(ar, "wmi command %d timeout, restarting hardware\n", + cmd_id); + queue_work(ar->workqueue, &ar->restart_work); + } + return ret; } -- 2.17.1