Received-SPF: pass (google.com: domain of linux-wireless+bounces-1717-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Kalle Valo <kvalo@kernel.org>
To: James Prestwood <prestwoj@gmail.com>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
  linux-wireless@vger.kernel.org,  ath11k@lists.infradead.org
Subject: Re: ath11k and vfio-pci support
References: <adcb785e-4dc7-4c4a-b341-d53b72e13467@gmail.com>
	<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>
	<df9fd970-5af3-468c-b1f1-18f91215cf44@gmail.com>
Date: Thu, 11 Jan 2024 15:11:07 +0200
In-Reply-To: <df9fd970-5af3-468c-b1f1-18f91215cf44@gmail.com> (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)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

James Prestwood <prestwoj@gmail.com> writes:

> Hi Kalle, Baochen,
>
> On 1/11/24 12:16 AM, Kalle Valo wrote:
>> Baochen Qiang <quic_bqiang@quicinc.com> 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 <prestwoj@gmail.com> 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