From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Fabio Estevam <festevam@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: <miriam.rachel.korenblit@intel.com>, <kvalo@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: Regression after migrating to 6.6.32
Date: Thu, 13 Jun 2024 15:10:35 +0800 [thread overview]
Message-ID: <d49fcc32-bfa8-41d2-8666-af6256b7b4b4@quicinc.com> (raw)
In-Reply-To: <CAOMZO5CMX_juW4-t6CSd2xdzXkFfBiamuSTjsTB80Ly_TUsxRA@mail.gmail.com>
On 6/13/2024 3:15 AM, Fabio Estevam wrote:
> Hi Johannes,
>
> On Wed, Jun 12, 2024 at 4:10 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>
>> Strange. Is there an IOMMU involved on this platform?
>
> IOMMU isn't available on i.MX8M as far as I know.
If IOMMU not present, likely the buffer is mapped by SWIOTLB. The iova 4215433216, aka 0xFB426800, is 2K aligned, which also supports such guessing. See definition of IO_TLB_SIZE.
>
> Interestingly, such a warning does not happen with the 5.10 kernel.
>
> I only noticed it yesterday, after migrating to 6.6.32.
>
> Thanks
>
next prev parent reply other threads:[~2024-06-13 7:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 11:46 Fabio Estevam
2024-06-11 12:52 ` Johannes Berg
2024-06-11 13:43 ` Fabio Estevam
2024-06-11 13:54 ` Johannes Berg
2024-06-11 14:32 ` Fabio Estevam
2024-06-11 14:50 ` Johannes Berg
2024-06-11 14:59 ` Fabio Estevam
2024-06-12 19:10 ` Johannes Berg
2024-06-12 19:15 ` Fabio Estevam
2024-06-13 6:58 ` Johannes Berg
2024-06-13 7:10 ` Baochen Qiang [this message]
2024-06-13 7:40 ` Johannes Berg
2024-06-13 9:51 ` Baochen Qiang
2024-06-13 10:36 ` Johannes Berg
2024-06-13 20:15 ` Fabio Estevam
2024-06-17 12:08 ` Will Deacon
2024-06-17 14:08 ` Fabio Estevam
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=d49fcc32-bfa8-41d2-8666-af6256b7b4b4@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=festevam@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/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
all inboxes | Powered by JetHome®