From: Kalle Valo <kvalo@codeaurora.org>
To: Wren Turkal <wt@penguintechs.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
regressions@lists.linux.dev,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Hemant Kumar <hemantk@codeaurora.org>,
Loic Poulain <loic.poulain@linaro.org>
Subject: Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310
Date: Fri, 27 Aug 2021 15:43:58 +0300 [thread overview]
Message-ID: <87o89j5a7l.fsf@codeaurora.org> (raw)
In-Reply-To: <d2795e7c-69cf-557d-19c4-f800c3a80997@penguintechs.org> (Wren Turkal's message of "Mon, 23 Aug 2021 09:17:19 -0700")
Wren Turkal <wt@penguintechs.org> writes:
> On 8/23/21 5:53 AM, Kalle Valo wrote:
>> Do you get the same mhi error as in the forum post?
>>
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Yes, I get that same message in my logs.
>
> FWIW, ath11k_pci now does not get loaded on boot. I can manually load
> it, but it doesn't seem to do anything.
Do you know if this automatic module loading is related to this qrtr
regression or a separate problem? Can you try Linus' tree and report if
the module load problem still exists? The qrtr regression is fixed now.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-08-27 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8cddf24-ecfc-088e-27f4-98cbbb5fb67c@penguintechs.org>
2021-08-23 12:53 ` 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310 Kalle Valo
2021-08-23 16:02 ` Nicolas Schichan
[not found] ` <87tujgqcth.fsf@codeaurora.org>
[not found] ` <87mtp47073.fsf_-_@codeaurora.org>
2021-08-26 14:38 ` [regression] " Greg Kroah-Hartman
2021-08-26 14:48 ` Jakub Kicinski
2021-08-26 15:00 ` Kalle Valo
2021-08-26 17:33 ` Kalle Valo
2021-08-26 18:12 ` Jakub Kicinski
2021-08-27 12:41 ` Kalle Valo
2021-08-30 16:04 ` Nicolas Schichan
2021-08-31 10:37 ` Kalle Valo
2021-08-27 12:46 ` Kalle Valo
2021-08-23 16:17 ` Wren Turkal
2021-08-27 12:43 ` Kalle Valo [this message]
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=87o89j5a7l.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=hemantk@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=wt@penguintechs.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).