From: Johannes Berg <johannes@sipsolutions.net>
To: Fabio Estevam <festevam@gmail.com>
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 08:58:26 +0200 [thread overview]
Message-ID: <82d2f2de67bf9284a124225b879c18790fb996ca.camel@sipsolutions.net> (raw)
In-Reply-To: <CAOMZO5CMX_juW4-t6CSd2xdzXkFfBiamuSTjsTB80Ly_TUsxRA@mail.gmail.com>
On Wed, 2024-06-12 at 16:15 -0300, 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.
Alright, so I don't know.
> Interestingly, such a warning does not happen with the 5.10 kernel.
Sure, but that's also _ancient_. There are >12k commits since then that
change arch/arm64/ alone ... And since we didn't change the driver, I
guess the issue is somewhere there?
But ... I see you're one of the NXP ARM64 kernel maintainers so you will
likely know better than me what's going on there :P
I guess you could also check the *virtual* address of the allocated
paged isn't also weirdly unaligned, but either way it's strange that the
arch/iommu/... gives an unaligned physical/IO-virtual address.
johannes
next prev parent reply other threads:[~2024-06-13 6:58 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 [this message]
2024-06-13 7:10 ` Baochen Qiang
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=82d2f2de67bf9284a124225b879c18790fb996ca.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=festevam@gmail.com \
--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®