From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8A14AC47258 for ; Thu, 11 Jan 2024 13:11:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References:Subject:Cc: To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Xk53MHcXaBc/qe4901eYqEK9cjk9W7j8opCQ74N4LDI=; b=AtWJtg3usouw7gpl+abp6dBw7o A0/8hf8fddW4hjeEAaml4rhOtT6hzYT4ZRC+V6RXm/E8USeLH796h/Yb9D8sc3V7x2ujTTzy36stV 4e25MGcEXfmVyB3BHFm50emTOyEQrU4NB2p6Hsp4Z/NKx9uKWT5was+LCgt8iK8bRAKOAqqr6Yadz i0HH90famH2q0BRHVDzLGAnkp/efaljaGXhZQK/hpIRwDy3YakZfyPnqr/LrU0FfGaqYkBx40AYjU GaYQW00ie0DKBbOK+8ip+jhh4KNMyfPxbjV7a/eItEkdHTL4haYmF6UeBpwBnhmXMaqPWyQ5JSD16 8vygysLg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rNuq4-0006fk-3B; Thu, 11 Jan 2024 13:11:16 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rNuq1-0006dn-0v for ath11k@lists.infradead.org; Thu, 11 Jan 2024 13:11:15 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id 8DA5DB8201F; Thu, 11 Jan 2024 13:11:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E759FC433A6; Thu, 11 Jan 2024 13:11:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704978670; bh=Xk53MHcXaBc/qe4901eYqEK9cjk9W7j8opCQ74N4LDI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=KJu+E5D6hDXtT0PQSkE7t4X3wZzElymcoTMLRiL/R9I2E9a75+ajSzpByNuICy3qs CKTBwG2FOrqYJ5Td8QFuscQAjQ3jdBAmgttGcZ7xZHuFu+hIMc/q3d3FBYLSdWvhLo 3obcOJLvkNMwhPRzAJkQjLVktWCfRFL65wEASNy0/rP/Ich7zdhGP0uebLjpez7kKX W6uAokqHECGXwqtnlCBLRbcqcgwSpJx6hyHxnFQb6a3YA9bzxCDtgJKlrwNdD9AiOD SX/OOJgX6ef7Rr2jB/OGL3e6pN3XpU4eyii6ELhBw2asPLUDsyCaAF/GLEH+43REBi cuGi9pZJYjI4g== From: Kalle Valo To: James Prestwood Cc: Baochen Qiang , linux-wireless@vger.kernel.org, ath11k@lists.infradead.org Subject: Re: ath11k and vfio-pci support References: <8734v5zhol.fsf@kernel.org> <87fa5220-6fd9-433d-879b-c55ac67a0748@gmail.com> <87r0ipcn7j.fsf@kernel.org> <356e0b05-f396-4ad7-9b29-c492b54af834@gmail.com> <26119c3f-9012-47bb-948e-7e976d4773a7@quicinc.com> <87mstccmk6.fsf@kernel.org> Date: Thu, 11 Jan 2024 15:11:07 +0200 In-Reply-To: (James Prestwood's message of "Thu, 11 Jan 2024 04:48:24 -0800") Message-ID: <8734v4auc4.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240111_051113_649028_25942C8E X-CRM114-Status: GOOD ( 14.77 ) X-BeenThere: ath11k@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "ath11k" Errors-To: ath11k-bounces+ath11k=archiver.kernel.org@lists.infradead.org James Prestwood writes: > Hi Kalle, Baochen, > > On 1/11/24 12:16 AM, Kalle Valo wrote: >> Baochen Qiang writes: >> >>> On 1/10/2024 10:55 PM, James Prestwood wrote: >>>> Hi Kalle, >>>> On 1/10/24 5:49 AM, Kalle Valo wrote: >>>>> James Prestwood writes: >>>>> >>>>>>> But I have also no idea what is causing this, I guess we are doing >>>>>>> something wrong with the PCI communication? That reminds me, you co= uld >>>>>>> try this in case that helps: >>>>>>> >>>>>>> https://patchwork.kernel.org/project/linux-wireless/patch/202312120= 31914.47339-1-imguzh@gmail.com/ >>>>>> Heh, I saw this pop up a day after I sent this and was wondering. Is >>>>>> this something I'd need on the host kernel, guest, or both? >>>>> On the guest where ath11k is running. I'm not optimistic that this wo= uld >>>>> solve your issue, I suspect there can be also other bugs, but good to >>>>> know if the patch changes anything. >>>> Looks the same here, didn't seem to change anything based on the >>>> kernel logs. >>>> >>> Could you try this? >>> >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm= it/drivers/net/wireless/ath/ath11k/pci.c?id=3D39564b475ac5a589e6c22c43a08cb= d283c295d2c >> This reminds me, I assumed James was testing with ath.git master branch >> (which has that commit) but I never checked that. So for testing please >> always use the master branch to get the latest and greatest ath11k: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/ >> >> There's a quite long delay from ath.git to official releases. > > Good to know, and I was not in fact using that branch. Rebuilt from > ath.git/master but still roughly the same behavior. There does appear > to be more output now though, specifically a firmware crash: > > [=C2=A0=C2=A0=C2=A0 2.281721] ath11k_pci 0000:00:06.0: failed to receive = control > response completion, polling.. > [=C2=A0=C2=A0=C2=A0 2.282101] ip (65) used greatest stack depth: 12464 by= tes left > [=C2=A0=C2=A0=C2=A0 3.306039] ath11k_pci 0000:00:06.0: Service connect ti= meout > [=C2=A0=C2=A0=C2=A0 3.307588] ath11k_pci 0000:00:06.0: failed to connect = to HTT: -110 > [=C2=A0=C2=A0=C2=A0 3.309286] ath11k_pci 0000:00:06.0: failed to start co= re: -110 > [=C2=A0=C2=A0=C2=A0 3.519637] ath11k_pci 0000:00:06.0: firmware crashed: = MHI_CB_EE_RDDM > [=C2=A0=C2=A0=C2=A0 3.519678] ath11k_pci 0000:00:06.0: ignore reset dev f= lags 0x4000 > [=C2=A0=C2=A0=C2=A0 3.627087] ath11k_pci 0000:00:06.0: firmware crashed: = MHI_CB_EE_RDDM > [=C2=A0=C2=A0=C2=A0 3.627129] ath11k_pci 0000:00:06.0: ignore reset dev f= lags 0x4000 > [=C2=A0=C2=A0 13.802105] ath11k_pci 0000:00:06.0: failed to wait wlan mode > request (mode 4): -110 > [=C2=A0=C2=A0 13.802175] ath11k_pci 0000:00:06.0: qmi failed to send wlan= mode > off: -110 Ok, that's progress now. Can you try next try the iommu patch[1] we talked about earlier? It's already in master-pending branch (along with other pending patches) so you can use that branch if you want. [1] https://patchwork.kernel.org/project/linux-wireless/patch/2023121203191= 4.47339-1-imguzh@gmail.com/ --=20 https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatc= hes