[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240426163317.4d908643@canb.auug.org.au>
Date: Fri, 26 Apr 2024 16:33:17 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Mike Rapoport <rppt@...nel.org>
Cc: Luis Chamberlain <mcgrof@...nel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Michael Ellerman <mpe@...erman.id.au>,
PowerPC <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: boot failure after merge of the modules tree
Hi Mike,
On Wed, 24 Apr 2024 12:14:49 +0300 Mike Rapoport <rppt@...nel.org> wrote:
>
> This should fix it for now, I'll rework initialization a bit in v6
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 1c4be3373686..bea33bf538e9 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -176,6 +176,7 @@ config PPC
> select ARCH_WANT_IRQS_OFF_ACTIVATE_MM
> select ARCH_WANT_LD_ORPHAN_WARN
> select ARCH_WANT_OPTIMIZE_DAX_VMEMMAP if PPC_RADIX_MMU
> + select ARCH_WANTS_EXECMEM_EARLY if EXECMEM
> select ARCH_WANTS_MODULES_DATA_IN_VMALLOC if PPC_BOOK3S_32 || PPC_8xx
> select ARCH_WEAK_RELEASE_ACQUIRE
> select BINFMT_ELF
I added the above to today's merge of the modules tree and it made the
boot failure go away.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists