Received-SPF: pass (google.com: domain of linux-kernel+bounces-212664-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Message-ID: <82d2f2de67bf9284a124225b879c18790fb996ca.camel@sipsolutions.net>
Subject: Re: iwlwifi: Regression after migrating to 6.6.32
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>
Date: Thu, 13 Jun 2024 08:58:26 +0200
In-Reply-To: <CAOMZO5CMX_juW4-t6CSd2xdzXkFfBiamuSTjsTB80Ly_TUsxRA@mail.gmail.com>
References: 
	<CAOMZO5A7+nxACoBPY0k8cOpVQByZtEV_N1489MK5wETHF_RXWA@mail.gmail.com>
	 <3fbb5317d9ff33ef1b60ca8297537335ce86a79d.camel@sipsolutions.net>
	 <CAOMZO5Aufe7zAE7TFVprvRreamYd9=RHjybjaEz2O9WaPksV=Q@mail.gmail.com>
	 <95163ee547da95964c16f87a38d3326ae4da3253.camel@sipsolutions.net>
	 <CAOMZO5CYDsh70u3To7HYXVki_MzzhFyCCHkigt_Es7o_+XG3oA@mail.gmail.com>
	 <7a8e220d77d7e30a0cfaf984404ef2f57eaa785f.camel@sipsolutions.net>
	 <CAOMZO5BktgtaSPzCf3WOOnkD2n+fj3FeQEfHeT7CYFL+tCHeaw@mail.gmail.com>
	 <fb60b7f5bcf5ba47be54398225075a5bfab7c141.camel@sipsolutions.net>
	 <CAOMZO5CMX_juW4-t6CSd2xdzXkFfBiamuSTjsTB80Ly_TUsxRA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.2 (3.52.2-1.fc40) 
Precedence: bulk
MIME-Version: 1.0

On Wed, 2024-06-12 at 16:15 -0300, Fabio Estevam wrote:
> Hi Johannes,
>=20
> On Wed, Jun 12, 2024 at 4:10=E2=80=AFPM Johannes Berg <johannes@sipsoluti=
ons.net> wrote:
>=20
> > Strange. Is there an IOMMU involved on this platform?
>=20
> 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