From: Bhaumik Bhatt <bbhatt@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [regressions] ath11k: v5.12.3 mhi regression
Date: Thu, 20 May 2021 10:38:12 -0700 [thread overview]
Message-ID: <3e8bac3b02e3549a55b7c9b78b699965@codeaurora.org> (raw)
In-Reply-To: <87r1i1h9an.fsf@codeaurora.org>
On 2021-05-20 05:36 AM, Kalle Valo wrote:
> Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> writes:
>
>> On Thu, May 20, 2021 at 12:02:40PM +0200, Greg KH wrote:
>>> On Thu, May 20, 2021 at 12:47:53PM +0300, Kalle Valo wrote:
>>> > Hi,
>>> >
>>> > I got several reports that this mhi commit broke ath11k in v5.12.3:
>>> >
>>> > commit 29b9829718c5e9bd68fc1c652f5e0ba9b9a64fed
>>> > Author: Bhaumik Bhatt <bbhatt@codeaurora.org>
>>> > Date: Wed Feb 24 15:23:04 2021 -0800
>>> >
>>> > bus: mhi: core: Process execution environment changes serially
>>> >
>>> > [ Upstream commit ef2126c4e2ea2b92f543fae00a2a0332e4573c48 ]
>>> >
>>> > Here are the reports:
>>> >
>>> > https://bugzilla.kernel.org/show_bug.cgi?id=213055
>>> >
>>> > https://bugzilla.kernel.org/show_bug.cgi?id=212187
>>> >
>>> > https://bugs.archlinux.org/task/70849?project=1&string=linux
>>> >
>>> > Interestingly v5.13-rc1 seems to work fine, at least for me, though I
>>> > have not tested v5.12.3 myself. Can someone revert this commit in the
>>> > stable release so that people get their wifi working again, please?
>>>
>>> How does the mhi bus code relate to a ath11k driver? What bus is
>>> that
>>> on?
>>>
>>
>> MHI is the transport used by the ath11k driver to work with the WLAN
>> devices
>> over PCIe.
>>
>> Regarding the bug, I'd suggest to wait for Bhaumik (the author of
>> 29b9829718c5)
>> to comment on the possible commit which needs backporting from
>> mainline.
>
> Ok, but if a quick fix is not available I think we should just revert
> this in the stable releases. I also got a report that v5.11.21 is
> broken:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=213055#c11
Please pick [1] as the dependency to [ Upstream commit
ef2126c4e2ea2b92f543fae00a2a0332e4573c48 ].
That is missing in older kernels and did not get backported.
This explains why 5.13.x works.
Thanks,
Bhaumik
---
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/bus/mhi/core?h=v5.13-rc2&id=4884362f6977fc05cbec736625665241c0e0732f
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2021-05-20 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:47 [regressions] ath11k: v5.12.3 mhi regression Kalle Valo
2021-05-20 10:02 ` Greg KH
2021-05-20 10:43 ` Manivannan Sadhasivam
2021-05-20 12:36 ` Kalle Valo
2021-05-20 17:38 ` Bhaumik Bhatt [this message]
2021-05-20 17:58 ` Greg KH
2021-05-20 18:04 ` Bhaumik Bhatt
2021-05-20 18:17 ` Greg KH
2021-05-24 5:56 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e8bac3b02e3549a55b7c9b78b699965@codeaurora.org \
--to=bbhatt@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).