linux-next: boot failure after merge of the modules tree

Stephen Rothwell sfr at canb.auug.org.au
Fri Apr 26 16:33:17 AEST 2024


Hi Mike,

On Wed, 24 Apr 2024 12:14:49 +0300 Mike Rapoport <rppt at kernel.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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20240426/a1f28c3d/attachment.sig>


More information about the Linuxppc-dev mailing list