Buildresult: powerpc-fixes/m68k-defconfig/m68k-gcc11 built on May 19 2023, 17:39

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

🌟 kisskb is no longer producing new builds, old results are still available.

Status:	OK
Date/Time:	May 19 2023, 17:39
Duration:	0:01:34.517185
Builder:	alpine2
Revision:	powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges (`8bf550499c94b27dae4b551df562a774c580e85b)`
Target:	powerpc-fixes/m68k-defconfig/m68k-gcc11
Branch:	powerpc-fixes
Compiler:	m68k-gcc11 (m68k-linux-gcc (GCC) 11.3.0 / GNU ld (GNU Binutils) 2.38)
Config:	defconfig (download)
Log:	Download original Possible warnings (3) remote: warning: multi-pack bitmap is missing required reverse index warning: The last gc run reported the following. Please correct the root cause warning: There are too many unreachable loose objects; run 'git prune' to remove them. Full Log # git rev-parse -q --verify 8bf550499c94b27dae4b551df562a774c580e85b^{commit} # git fetch -q -n -f git://gitlab.ozlabs.ibm.com/linuxppc/linux.git fixes-test remote: warning: multi-pack bitmap is missing required reverse index warning: The last gc run reported the following. Please correct the root cause and remove .git/gc.log. Automatic cleanup will not be performed until the file is removed. warning: There are too many unreachable loose objects; run 'git prune' to remove them. # git rev-parse -q --verify 8bf550499c94b27dae4b551df562a774c580e85b^{commit} 8bf550499c94b27dae4b551df562a774c580e85b # git checkout -q -f -B kisskb 8bf550499c94b27dae4b551df562a774c580e85b # git clean -qxdf # < git log -1 # commit 8bf550499c94b27dae4b551df562a774c580e85b # Author: Michael Ellerman <mpe@ellerman.id.au> # Date: Fri May 19 16:44:10 2023 +1000 # # powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges # # Commit 1e8fed873e74 ("powerpc: drop ranges for definition of # ARCH_FORCE_MAX_ORDER") removed the limits on the possible values for # ARCH_FORCE_MAX_ORDER. # # However removing the ranges entirely causes some common work flows to # break. For example building a defconfig (which uses 64K pages), changing # the page size to 4K, and rebuilding used to work, because # ARCH_FORCE_MAX_ORDER would be clamped to 12 by the ranges. # # With the ranges removed it creates a kernel that builds but crashes at # boot: # kernel BUG at mm/huge_memory.c:470! # Oops: Exception in kernel mode, sig: 5 [#1] # ... # NIP hugepage_init+0x9c/0x278 # LR do_one_initcall+0x80/0x320 # Call Trace: # do_one_initcall+0x80/0x320 # kernel_init_freeable+0x304/0x3ac # kernel_init+0x30/0x1a0 # ret_from_kernel_user_thread+0x14/0x1c # # The reasoning for removing the ranges was that some of the values were # too large. So take that into account and limit the maximums to 10 which # is the default max, except for the 4K case which uses 12. # # Fixes: 1e8fed873e74 ("powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER") # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # < /opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux-ld --version # < git log --format=%s --max-count=1 8bf550499c94b27dae4b551df562a774c580e85b # < make -s -j 160 ARCH=m68k O=/kisskb/build/powerpc-fixes_m68k-defconfig_m68k-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux- defconfig # < make -s -j 160 ARCH=m68k O=/kisskb/build/powerpc-fixes_m68k-defconfig_m68k-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux- help # make -s -j 160 ARCH=m68k O=/kisskb/build/powerpc-fixes_m68k-defconfig_m68k-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux- olddefconfig # make -s -j 160 ARCH=m68k O=/kisskb/build/powerpc-fixes_m68k-defconfig_m68k-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.3.0-nolibc/m68k-linux/bin/m68k-linux- Completed OK # rm -rf /kisskb/build/powerpc-fixes_m68k-defconfig_m68k-gcc11 # Build took: 0:01:34.517185

© Michael Ellerman 2006-2018.